Agent Skill Inventory

Use the local runtime as the source of truth instead of guessing from memory.

Preferred entrypoint:

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

Provider rules

• OpenClaw: prefer openclaw skills list --eligible --json, openclaw skills check --json, and openclaw skills info <name> --json for readiness and exact baseDir.
• Codex: inspect ${CODEX_HOME:-~/.codex}/skills and ignore hidden system folders like .system/.
• Claude Code: inspect ~/.claude/skills and ./.claude/skills when project-local skills may exist.

Workflow

1. Inventory installed skills for the requested provider or for all supported providers.
2. Record the exact path for each relevant skill.
3. Compare local skills with the marketplace catalog.
4. Group results into:

• already on the marketplace
• portable local skills worth publishing
• bundled, blocked, secret-dependent, or machine-specific skills to skip for now

1. If the user wants the same skill available in another runtime, use forgedemy transfer <slug> --from <provider> --to <provider>.
2. Hand the factual inventory to the agent so it can inspect the strongest candidates before proposing listings.

Publishing heuristics

• Prefer local workspace skills over bundled runtime defaults.
• OpenClaw workspace skills are the strongest custom signal; bundled and extra skills are not user-created defaults.
• In Codex and Claude Code, installed skills are user-managed by default, but hidden system folders and obvious imported/bootstrap bundles should be excluded.
• Be cautious with hardware-bound, bot-account-bound, or private internal automation.
• If a skill depends on local secrets, a specific host, or a single account, call that out before recommending publication.
• If a local skill already has a marketplace match, report the match instead of treating it as a new listing candidate.
• Look for user-specific wording in the body: project names, channels, brands, devices, hosts, or personal workflow rules. These are strong custom signals.

Response contract

When reporting back, include:

• which providers were inspected
• the exact path for each cited skill
• whether the skill already matches a marketplace listing
• a short reason why it is or is not a good publication candidate
• any publication risks that should be checked before publishing

Do not invent final listing titles, prices, or descriptions inside the inventory step. After inventory, the agent should open the actual skill files and then propose up to two listings with package path, entrypoint, title, price, and short description.