npbuilds Skill Library Gateway
Use the plugin-provided skill-library MCP server as the normal source. Treat the
library's SKILL.md files as shared methodology, not as Codex installation files.
Select a skill
- For an explicit skill name, call
get_skill_detailsif disambiguation is useful, then callget_skillwith that exact name. - For a task or fuzzy description, reduce the goal to 2-6 generic domain and
task keywords before calling
search_skills. Never include personal names, secrets, unpublished details, document contents, or other sensitive text in a search query. Inspect descriptions and domain tags rather than blindly accepting the first result, then select one primary skill. - Add at most two supporting skills when their roles are distinct and materially useful. Avoid loading a large bundle of loosely related skills.
- Use
list_skillsorget_system_overviewonly for browsing, audits, or broad questions about the library itself.
Load the primary skill with include_references: false first. Reload with
include_references: true only when its procedure requires bundled references or
agent definitions. This keeps context use proportional to the task.
Apply it in Codex
Follow the loaded skill's methodology while adapting runtime-specific mechanics:
| Claude-authored instruction | Codex behavior |
|---|---|
WebSearch / WebFetch |
Use the available web or browser tools. |
Read / Write / Edit |
Use Codex filesystem tools within the user's authorized scope. |
Bash / Grep / Glob |
Use shell tools; prefer rg for text and file search. |
Agent / subagents |
Delegate only when the current harness and instructions allow it; otherwise work inline. |
| Claude slash command | Follow the underlying workflow directly. |
allowed-tools frontmatter |
Treat as compatibility metadata, not permission or a hard requirement. |
Preserve the skill's domain reasoning, ordering, quality criteria, and output contract. Higher-priority instructions, the user's request, safety constraints, and actual tool availability always take precedence.
Execute and report
- Briefly tell the user which library skill or skills are being applied.
- Complete the task rather than merely summarizing the loaded instructions.
- Keep canonical skill files unchanged unless the user explicitly asks to edit the library.
- If a loaded skill requires unavailable capabilities, adapt the procedure and disclose any material limitation in the final result.
Fallback
If the MCP server is unavailable and the current workspace contains the canonical
library, locate candidates in data/registry.json or skills/**/SKILL.md, then
read the selected files locally and use the same adaptation rules. Otherwise,
state that the library connection is unavailable and continue with the best
general approach when possible.