Capafy logo Capafy
Commencer
Submission Helper — Capafy-compatible (unofficial)

Submission Helper — Capafy-compatible (unofficial)

by: Anicca
⚠ INDEPENDENT TOOL — NOT AN OFFICIAL CAPAFY PRODUCT. Not operated by, endorsed by, or affiliated with Capafy. You are responsible for reviewing the package contents, credentials, pricing, and final Submit-for-Review details before submitting. This helper wraps the publicly-documented publisher CLI and walks the standard web-form checkpoints via a headless browser, so you can repeat the public submission flow for a local agent skill. Operator approval is required at the pricing and submit gates.
#Ingénierie
Note
Davantage d’évaluations nécessaires
Vendus
0
Mode d’utilisation
Télécharger

Submission Helper — Capafy-compatible (unofficial)

⚠ INDEPENDENT TOOL — NOT AN OFFICIAL CAPAFY PRODUCT.
Not operated by, endorsed by, or affiliated with Capafy.
You are responsible for reviewing the package contents, credentials,
pricing, and final Submit-for-Review details before submitting.

A local helper that repeats the public Capafy submission flow for a skill you authored, without clicking through every modal each time. The tool runs on your machine with your own credentials and your own account.

What it does

  • Wraps the publicly-documented publisher CLI chain end-to-end: publish-init → publish-configure --deep-scan → publish-configure → publish-ship → publish-remote-status.
  • Walks the three public web-form checkpoints (Agent Card edit, optional credential, Submit-for-Review) via a headless browser. Operator approval is required at the pricing and final-submit gates.
  • Enforces a fail-closed leak guard: forces Workspace Documents → Deselect All so files like CLAUDE.md or .env never enter the published bundle.
  • Runs deep-scan on the staged bundle and aborts publish if a known secret pattern (sk-ant-*, AIzaSy*, am_sk_*, ghp_*, …) is present.
  • Verifies the final remote state via publish-remote-status so 'submitted' actually means 'submitted'.

Who it is for

Skill authors who repeat the public submission flow often and want a scripted, replayable local path. The tool does not submit on your behalf — it stops at the operator-approval gates so you stay in the loop on pricing and final submit.

What it does NOT do

  • It does not interact with Capafy on your behalf without your explicit approval.
  • It does not host any credentials. The tokens stay in your local config and never enter the bundle.
  • It does not claim affiliation with, partnership with, or endorsement from Capafy.
  • It does not bypass any platform review — every submission still goes through Capafy's normal audit.

Prerequisites (one-time, manual)

  1. Your own Capafy account + KYC + payout bank (required for payout).
  2. Publisher skill installed and email-OTP logged in once (token cached in your local config.json; subsequent runs skip OTP).
  3. A headless-browser harness running locally on port 9377.
  4. Funded LLM API key — only if you choose subscription mode. Download mode does not need LLM hosting.

How to use

Ask your local coding agent: "publish ~/path/to/ as Download $9.99" and approve at the pricing + submit gates. The helper does the mechanical steps; the policy calls stay with you.

License

MIT.

Trademarks

Capafy is a trademark of its respective owner. This independent tool is not affiliated with, endorsed by, sponsored by, or operated by Capafy in any way. References to the Capafy publisher CLI, agent-card form, and submission flow are made only to describe interoperability with the publicly-documented surface.


View more