using-skill-engine

An entry-point skill for Skill Engine, which checks whether the current project has a contextualizer installed and sends the request to the appropriate setup or workflow.

In plain words
What is it for?
Use it for first-time setup or when you mention Skill Engine without naming a specific workflow; it also checks for unfinished proposals.
Why use it?
It prevents you from having to know which Skill Engine workflow to run first.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/nick-railsback/skill-engine/using-skill-engine
Any agent
npx skills add nick-railsback/skill-engine --skill using-skill-engine
Clone the repo
git clone --depth 1 https://github.com/nick-railsback/skill-engine

Made for: Claude Code, Codex.

Per session 101 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,634 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00101 $0.01634
Opus 5 $0.00051 $0.00817
Sonnet 5 $0.00020 $0.00327
Haiku 4.5 $0.00010 $0.00163

Measured 2d ago against content hash dde346e1374c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

using-skill-engine scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugin/skill-engine/skills/using-skill-engine/SKILL.md · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Using the skill engine

This is the entry-point skill. It detects whether the current directory holds a contextualizer that has already been set up, and routes to the matching workflow.

Routing

When invoked, do the following in order. A contextualizer is installed at one of three install levels (~/.claude/skills/, ~/.claude/local/skills/, or <repo>/.claude/skills/); its research/.research-state.json is the canonical setup-state marker.

Locate the contextualizer root by searching all three install levels:

ctx_roots=$(
  for root in "$HOME/.claude/skills" "$HOME/.claude/local/skills" "$PWD/.claude/skills"; do
    [ -d "$root" ] || continue
    find "$root" -mindepth 1 -maxdepth 1 -type d -name '*-context' 2>/dev/null
  done
)
# `|| true`: grep -c prints 0 but exits 1 on zero matches — without the
# guard a pipefail/errexit shell dies here instead of reaching case 1.
ctx_count=$(printf '%s\n' "$ctx_roots" | grep -c . || true)

Pending-proposal pre-step (runs before case dispatch)

Before dispatching to a workflow, check for pending proposals — any *-context.proposed/ directory that DISCOVER or REFRESH left behind under the same three install roots:

proposed_dirs=$(
  for root in "$HOME/.claude/skills" "$HOME/.claude/local/skills" "$PWD/.claude/skills"; do
    [ -d "$root" ] || continue
    find "$root" -mindepth 1 -maxdepth 1 -type d -name '*-context.proposed' 2>/dev/null
  done
)

If any proposed dirs exist and the requested workflow is a mutating one (discover, refresh, new-reference), surface a one-line note naming each proposal and the three commands that gate its disposition, then exit without dispatching (the note is the entire output):

Pending proposal at <path>. Run /skill-engine:review <slug>, /skill-engine:apply <slug>, or /skill-engine:discard <slug> before re-running discover/refresh.

Rationale: re-running DISCOVER or REFRESH while a proposed dir already exists would either overwrite the pending changes silently or surface a confusing diff. The user is the right one to decide whether to promote, discard, or keep iterating; the router refuses to choose for them. The pre-step short-circuits before any case-1/case-2/case-3/case-4 branch fires.

Read the full file on GitHub · 135 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 135 lines · 101 tokens per session scan A dde346e1374c

Subscribe to this mod's changes

using-skill-engine is a skill published in the GitHub repository nick-railsback/skill-engine (2 stars, last pushed 25d ago), licensed MIT. It adds 101 tokens to every session and 1,634 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

skill-creator

Create or improve Zhin Agent skills (SKILL.md). Use when asked to add a skill, write SKILL.md, document a repeatable agent workflow, or refine skill frontmatter/keywords. Triggers: 创建技能, 写 SKILL, skill-creator, 加 skill.

zhinjs/zhin · 61 tokens

skill-sync-checker

Detects content drift between skill files and their source documents. Helps maintain skills that are derived from other documentation by comparing content and flagging outdated sections.

kanyun-inc/reskill · 35 tokens

tech-design-generation

Generates professional Technical Design Documents following industry-standard engineering practices. This skill activates when the user asks to write a technical design, create an architecture design, draft a design doc, write a technical proposal, do system design, create a technical design document, write an RFC…

tercel/spec-forge · 110 tokens

test-cases-generation

Generates structured test case sets with multi-dimensional coverage from project code analysis or specification documents. This skill activates when the user asks to write test cases, generate tests, supplement tests, create test coverage, or improve test completeness. It auto-scans the project to extract testable…

tercel/spec-forge · 132 tokens

idea

Use when exploring a new idea before writing formal specifications. Guides users through iterative discovery, research, and critical analysis to crystallize vague ideas into validated requirement drafts. Includes anti-pseudo-requirement checks, competitive research, demand evidence gathering, and "What if we don't…

tercel/spec-forge · 100 tokens

test-plan-generation

Generates professional Test Plan and Test Cases documents following IEEE 829 test documentation standards, ISTQB testing methodologies, and Google Testing Blog best practices. This skill activates when the user asks to write a test plan, create test cases, draft a test plan document, create a test cases document…

tercel/spec-forge · 119 tokens