okf-agent-skills

Project Agent Skills repositories into queryable OKF graphs and DuckDB audit views.

1|Updated May 8, 2026
One-click install
npx skills add https://github.com/franklinbaldo/skills --skill okf-agent-skills-franklinbaldo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: okf-agent-skills
Source: https://github.com/franklinbaldo/skills/tree/main/okf-agent-skills
Command: npx skills add https://github.com/franklinbaldo/skills --skill okf-agent-skills-franklinbaldo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires cyclopts, duckdb, and includes scripts (resource) and references (resource) components.

What problem does it solve? Auditing a growing collection of Agent Skills by hand is error-prone: dependencies between skills, unrouted mentions, missing routing evals, and oversized entry points are hard to see from raw Markdown. This Skill turns a skills repository into a deterministic, queryable inspection layer without changing the authored SKILL.md files. ## Core Features & Use Cases - Static projection: Discovers every SKILL.md, its resources, authored Markdown links, routing eval cases, and semantic sibling-skill mentions, then emits a disposable OKF bundle with RFC 0006 DuckDB schema contracts. - Graph and relational analysis: Compiles the bundle with okf-parser to produce dependency graphs and a DuckDB database, keeping authored links distinct from reviewed mentions with full source provenance. - Canonical audit views: Ships typed SQL views for eval coverage, resolved skill relations, mentions without edges, isolated skills, and resource surface, exported as a JSON report. - Use Case: Point it at a skills monorepo to find which skills lack routing evals, which are isolated from the dependency graph, and which scripts are never referenced, before deciding what to refactor. ## Quick Start Ask the agent to project this skills repository with scripts/project.py into a derived bundle, compile it with okf-parser into DuckDB, and run the typed audit to report eval coverage and isolated skills.

Frequently Asked Questions about okf-agent-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze dependencies between Agent Skills in a repository?▼

Run scripts/project.py against the skills root to build a derived OKF bundle, then compile it with okf-parser graph. Authored Markdown links become resolved edges while semantic mentions stay as separate observations with source provenance.

How do I check which skills lack routing eval coverage?▼

Build the DuckDB artifact with okf-parser duckdb, then run scripts/run_typed_audit.py. The eval_coverage view reports per-skill eval counts, positive and negative trigger cases, and flags skills with no routing evals.

Does this tool modify the source SKILL.md files?▼

No. Source skills remain authoritative and are never mutated during inspection. The projection is a disposable derived bundle, and the scripts only read source files without executing any scripts belonging to audited skills.

What dependencies are required to run the full audit pipeline?▼

The projection frontend needs only Python 3.11 with cyclopts. Full relational inspection requires a current okf-parser installation, and the typed audit views additionally require the duckdb Python package.

Can static analysis prove that skill routing works correctly?▼

No. The projection only captures structural facts like links, mentions, and eval cases. Runtime routing quality is deferred to real-use postmortems and feedback issues, with static evals serving only as regression memory.