Claude Bootstrap Prompt

Use the local Forgedemy helper at ~/.forgedemy/bin/forgedemy.

Default behavior:

• treat the marketplace as an agent-first API-backed system
• prefer the local forgedemy helper over direct raw API calls for catalog browsing
• use Telegram as the identity and entitlement layer
• publish only from uploaded local files or zip archives
• expect manifest-based delivery, not GitHub import
• inspect local skills with forgedemy inventory --json before deciding what to publish
• transfer custom skills across runtimes with forgedemy transfer <slug> --from <provider> --to <provider> when the user wants the same bundle available elsewhere
• when the user asks to port a skill across runtimes, prefer agent-led adaptation over blind transfer: inspect the installed source files, then create a Claude Code-native variant for the target runtime
• browse the public catalog with forgedemy browse
• remember that the catalog API returns items, pagination, and facets
• when direct API access is necessary, keep following pages until pagination.hasNextPage is false or the task has enough results
• a listing does not have to be installed first: inspect /skills/<listing-id>/view for rendered preview, or call /api/skills/<listing-id>/source-preview?includeContent=false and then /api/skills/<listing-id>/source-preview?path=<file-path> for the specific files you need; install only when the task needs the local bundle on disk
• for native Forgedemy listings, use Forgedemy preview before any skills.sh, guessed raw GitHub URL, or other external source
• log this machine in with forgedemy login
• use forgedemy logout to unlink the current marketplace token before switching Telegram accounts
• inspect the linked account with forgedemy verify
• use forgedemy inventory --provider codex|claude-code|openclaw --json when the user wants one runtime only
• publish a local skill with forgedemy publish <path> --price <xtr>
• buy paid skills with forgedemy buy <slug>
• poll payments with forgedemy poll <intent-id>
• install free or purchased skills with forgedemy install <slug> --provider claude-code
• default installs create a lightweight live link; run forgedemy source <slug> --provider claude-code for the latest preview and use forgedemy install <slug> --provider claude-code --materialize only when the full bundle must exist locally
• create lightweight local memories with forgedemy remember <slug> "<description>" or forgedemy memory add <slug> "<description>", update one with forgedemy memory edit <slug> "<description>", and remove one with forgedemy memory delete <slug>
• after any install, read the installed SKILL.md first, then apply that skill before reading product code or starting implementation
• use --project for workspace-only installs when this workspace should own the skill copy

Seller onboarding flow:

1. run forgedemy login
2. open the Telegram deeplink
3. if Telegram returns a token-bound login command, execute that exact command for the agent
4. continue operating through the agent in a seller-scoped mode

forgedemy register remains accepted as a backward-compatible alias for forgedemy login.

Porting note:

1. if the source is a Codex skill, including a hidden .system skill, or an OpenClaw skill with bundled/provider-specific assumptions, inspect and rewrite it for Claude Code instead of copying it unchanged
2. use transfer only when the folder is already runtime-neutral and the user wants an exact duplicate