LoomLoom Market SkillBot
Generated from a LoomLoom Market listing snapshot.
- Listing ID: "019f5ada-e317-7022-86e5-e0a6588deeac"
- Display name snapshot: "降低论文AIGC"
- Description snapshot: "将 5000 字以内的论文或学术文档改写为更自然、通俗的表达，同时保持专业性并保留核心术语、数据、公式、引文和结论；不承诺任何 AIGC 检测结果。"
Discover the current input contract
Choose an available Python 3.9 or later launcher for the current system. On Windows, prefer py -3 and then python; on macOS or Linux, prefer python3 and then python. Use that launcher in place of <python> below.
Run:
<python> scripts/loomloom_skill.py --describe
Use the returned inputSchemaSnapshot to construct one JSON object or a non-empty array of JSON objects.
Authenticate before paid execution
Run <python> scripts/loomloom_skill.py --auth-status before paid execution. The command verifies only credentials that match this package's fixed Server; it never reveals a credential or opens a browser. If it returns authenticated, continue. If it returns browser_login_required, ask the user whether they want to sign in and do not start or show browser authorization before they explicitly agree. Only after agreement, run <python> scripts/loomloom_skill.py --login and keep it running until the credential is verified. If it returns api_token_required or api_token_rejected, tell the user to configure the reported tokenEnv outside the Agent conversation; never ask them to paste a Token into chat.
Execute
Save the input as JSON, then run:
<python> scripts/loomloom_skill.py --input-json input.json
The script fetches the current public Listing version, requests a quote, checks balance, and requires explicit confirmation before submitting a paid run. For non-interactive use, pass --confirm-max-payable-t with the exact latest quoted amount. It then waits for completion and writes one JSON object containing run, Market usage, and result rows to stdout.
The package uses the LoomLoom CLI credential contract without requiring the CLI executable. It matches this package's fixed Server to a local config.json profile, prefers that profile's token_env API Key, and then uses its saved browser credential. It verifies every credential against the fixed Server. Normal execution never starts browser login implicitly. A browser callback alone is not final login success.
Never print, copy, or send the credential to another Server. Only a verified browser credential may be persisted in the LoomLoom CLI config; API Keys remain in environment variables. Authentication, quote, confirmation, execution errors, and recharge guidance are written to stderr. A 401 or 403 means only that the credential was not accepted by the configured Server; do not claim that the account is banned.
