1---
2name: agent-skill-inventory
3description: Inspect installed skills across Codex, Claude Code, and OpenClaw, locate their exact directories on the current machine, and separate portable publishable skills from bundled, blocked, or machine-specific ones. Use when a user asks what skills they already have, where those skills live, or which ones they could publish to a marketplace.
4allowed-tools: Bash, Read
5---
6 
7# Agent Skill Inventory
8 
9Use the local runtime as the source of truth instead of guessing from memory.
10 
11Preferred entrypoint:
12 
13- `forgedemy inventory --json`
14- `forgedemy inventory --provider codex`
15- `forgedemy inventory --provider claude-code`
16- `forgedemy inventory --provider openclaw`
17 
18## Provider rules
19 
20- OpenClaw: prefer `openclaw skills list --eligible --json`, `openclaw skills check --json`, and `openclaw skills info <name> --json` for readiness and exact `baseDir`.
21- Codex: inspect `${CODEX_HOME:-~/.codex}/skills` and ignore hidden system folders like `.system/`.
22- Claude Code: inspect `~/.claude/skills` and `./.claude/skills` when project-local skills may exist.
23 
24## Workflow
25 
261. Inventory installed skills for the requested provider or for all supported providers.
272. Record the exact path for each relevant skill.
283. Compare local skills with the marketplace catalog.
294. Group results into:
30   - already on the marketplace
31   - portable local skills worth publishing
32   - bundled, blocked, secret-dependent, or machine-specific skills to skip for now
335. If the user wants the same skill available in another runtime, use `forgedemy transfer <slug> --from <provider> --to <provider>`.
346. Hand the factual inventory to the agent so it can inspect the strongest candidates before proposing listings.
35 
36## Publishing heuristics
37 
38- Prefer local workspace skills over bundled runtime defaults.
39- OpenClaw workspace skills are the strongest custom signal; bundled and extra skills are not user-created defaults.
40- In Codex and Claude Code, installed skills are user-managed by default, but hidden system folders and obvious imported/bootstrap bundles should be excluded.
41- Be cautious with hardware-bound, bot-account-bound, or private internal automation.
42- If a skill depends on local secrets, a specific host, or a single account, call that out before recommending publication.
43- If a local skill already has a marketplace match, report the match instead of treating it as a new listing candidate.
44- Look for user-specific wording in the body: project names, channels, brands, devices, hosts, or personal workflow rules. These are strong custom signals.
45 
46## Response contract
47 
48When reporting back, include:
49 
50- which providers were inspected
51- the exact path for each cited skill
52- whether the skill already matches a marketplace listing
53- a short reason why it is or is not a good publication candidate
54- any publication risks that should be checked before publishing
55 
56Do 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.
57