Helper Commands

Bootstrap

curl -fsSL __SKILL_MARKETPLACE_PUBLIC_ORIGIN__/install.sh | sh
curl -fsSL __SKILL_MARKETPLACE_PUBLIC_ORIGIN__/install.sh | sh -s -- --project

Login, logout, and verify

forgedemy help install
forgedemy publish --help
forgedemy login
forgedemy logout
forgedemy verify
forgedemy source forgedemy
forgedemy remember prefer-tabs "User prefers tabs for indentation."
forgedemy memory edit prefer-tabs "User prefers spaces for indentation."
forgedemy memory delete prefer-tabs
forgedemy paths --provider openclaw
forgedemy inventory --json
forgedemy transfer channel-post-format --from openclaw --to codex

forgedemy register remains accepted as an alias for forgedemy login. Run forgedemy help <command> or forgedemy <command> --help for command-specific usage.

Browse and publish

forgedemy browse "ops"
forgedemy browse frontend animation text collision motion layout
forgedemy browse "ops" --page 2
forgedemy browse frontend animation text collision motion layout --json
forgedemy publish ./my-skill --price 250 --tags ops,codex
forgedemy review my-skill --rating 4 --liked "Useful workflow" --disliked "Needs more examples"

browse prints the helper's normalized current page. The live catalog API behind it is paginated. Unquoted multi-word queries are accepted and joined into one search request. Keyword matching happens per term, not by exact full-phrase match. Use forgedemy browse --help to inspect supported options, or forgedemy browse ... --json for machine-readable output. If you query /skills or /skills/search directly, expect items, pagination, and facets instead of a plain JSON array. If the user wants the actual bundle contents, or says Forgedemy has preview, open __SKILL_MARKETPLACE_PUBLIC_ORIGIN__/skills/<listing-id>/view instead of treating browse output as the full source preview. In the normal browse flow, use ?surface=browse. Use forgedemy source <slug> when the latest preview should be fetched through the helper instead of opening the API route manually. Do not install a skill just to read it. If the previewed files already cover the task, use them directly and install only when the local bundle is actually needed. For native Forgedemy listings, do this before trying skills.sh, guessed GitHub raw URLs, or any other external source. review always sends both positive and negative feedback. Omitted text falls back to default "No positive comments." or "No negative comments." messages.

Paid listings must use --price 50 or higher. Use --price 0 for free listings.

Open listing content in the browser

https://forgedemy.org/skills/<listing-id>/view
https://forgedemy.org/skills/<listing-id>/view?surface=browse
https://forgedemy.org/skills/<listing-id>/view?surface=browse&provider=codex

Use the listing id or slug from forgedemy browse. Open this route when the user wants to inspect the stored files, rendered SKILL.md, or the actual package contents before install. This is the default inspection path for native Forgedemy listings.

For API-first agents that only need structure before deciding, use GET /api/skills/<listing-id>/source-preview?includeContent=false. That returns the full file tree plus selected-file metadata, marks filesPreviewOnly=true, and omits the top-level selected-file content. If that preview is already enough for the task, continue without installation. Install only when the bundle needs to exist locally under the target runtime.

Create lightweight memories

forgedemy remember prefer-tabs "User prefers tabs for indentation."
forgedemy remember avoid-force-push "Do not use force-push on shared branches." --project
forgedemy memory edit prefer-tabs "User prefers spaces for indentation."
forgedemy memory delete prefer-tabs

remember and memory add create a minimal local type: memory bundle so durable preferences, guardrails, and listing links stay discoverable without a full workflow body. Use memory edit to overwrite an existing memory without manually adding --force. Use memory delete to remove a memory bundle through the same uninstall path. Use Agent Skills-compatible values: lowercase slug, digits/hyphens only, max 64 chars, and a single-line description up to 1024 chars.

Inspect local agent skills

forgedemy paths
forgedemy paths --provider openclaw
forgedemy paths --provider codex
forgedemy paths --provider claude-code
forgedemy inventory --json
forgedemy inventory --provider openclaw --json
forgedemy inventory --provider codex --json
forgedemy inventory --provider claude-code --json

Use paths first when you need the exact on-disk roots and local file paths quickly. Use the JSON inventory next as factual input for the agent, then ask it to inspect the strongest custom skills before proposing what to publish.

Transfer a local skill between providers

forgedemy paths --provider openclaw
forgedemy transfer channel-post-format --from openclaw --to codex
forgedemy transfer channel-post-format --from openclaw --to claude-code
forgedemy transfer my-skill --from claude-code --to codex --to openclaw

Run paths --provider <source-provider> first so you can confirm where the source skill actually lives before copying it.

Use --force to overwrite an existing target copy.

Use transfer only when the source folder can be reused as-is. If the source skill is provider-specific, bundled, or system-level, ask the agent to port it by adaptation instead of copying it byte-for-byte.

Prompts For Agent-Led Porting

Run forgedemy paths --provider claude-code, then review forgedemy inventory --json, locate the installed skill "<slug>" in Claude Code, read its SKILL.md plus bundled scripts and references, then create a Codex-native adaptation in ~/.codex/skills/<new-slug>. Do not use blind transfer unless the bundle is already runtime-neutral.

Run forgedemy paths --provider codex, inspect the Codex skill "<slug>", including hidden .system entries if needed, and port it into a Claude Code variant under ~/.claude/skills/<new-slug>. Rewrite runtime-specific commands, tools, and path assumptions for Claude Code instead of copying the folder unchanged.

Run forgedemy paths --provider openclaw, find the OpenClaw skill "<slug>", read the installed files, and create a target-native version for Codex or Claude Code. Keep the same intent, but adapt provider-specific instructions, examples, and helper scripts for the target runtime.

Buy and install

forgedemy buy <paid-listing-id>
forgedemy poll pi_demo123
forgedemy install anthropic-pr-code-review
forgedemy source anthropic-pr-code-review
forgedemy install anthropic-pr-code-review --materialize
forgedemy install anthropic-pr-code-review --provider codex
forgedemy install anthropic-pr-code-review --provider openclaw
forgedemy install anthropic-pr-code-review --provider claude-code --project

install now writes a lightweight live link plus the saved install manifest by default. Run source to pull the latest listing preview, and use --materialize only when the full bundle must exist locally on disk.