Agent Skills

A personal collection of agent skills — both custom-authored and cherry-picked from upstream repos — installable as a single package.

📚 Read the docs for the full guide, conventions, and skill index.

Install

# Install all skills bundled in this repo into your project's
# .agents/skills/ directory.
npx skills@latest add daviddwlee84/agent-skills/skills

Note The trailing /skills matters. Without it, npx skills will look in .agents/skills/ of the upstream repo, which contains a different layout. The skills/ suffix points the installer at the skills/local/, skills/owned/, and skills/vendor/ trees.

This is the recommended cross-agent install path. Project installs place the canonical skill content under .agents/skills/, which Codex reads directly; Claude Code receives its corresponding .claude/skills/ links.

Heads-up — upstream picker bug. npx skills' interactive multiselect glitches once the skill list is long enough to scroll: options render duplicated and the selection state gets corrupted (vercel-labs/skills#969). This repo ships enough skills to trigger it. Until it's fixed upstream, skip the picker:

# Install everything, non-interactively (no picker)
npx skills@latest add daviddwlee84/agent-skills/skills --yes

# List names from a disposable directory. In an existing agent-managed
# project, [email protected] may reconcile .agents/skills even with --list.
scratch="$(mktemp -d)"
(cd "$scratch" && npx skills@latest add daviddwlee84/agent-skills/skills --list)
rm -rf "$scratch"

# Install one skill by name.
npx skills@latest add daviddwlee84/agent-skills/skills --skill clash-proxy-api

Optional: native Claude Code and Codex marketplaces

A local checkout can expose the same category catalog through either native plugin CLI:

git clone https://github.com/daviddwlee84/agent-skills.git

# Claude Code
claude plugin marketplace add ./agent-skills/skills
claude plugin install version-control@daviddwlee84-skills

# Codex (verified with 0.147.0)
codex plugin marketplace add ./agent-skills/skills
codex plugin add version-control@daviddwlee84-skills

Both native routes install a whole category plugin (version-control in this example), not an arbitrary single skill. Codex reads the existing Claude-format marketplace and generates its .codex-plugin/plugin.json adapter inside the plugin cache; this repository does not need to maintain that second manifest. Keep using npx skills when you want one skill or a cross-agent installation.

Pass the checkout's skills/ directory, not the repository root: the catalog intentionally lives under skills/.claude-plugin/ for the npx subpath above, and both native CLIs require a supported manifest at the marketplace source root.

What's in here

The quantitative-finance marketplace group contains quantatitive-factor-researcher, vectorbt, and nautilus-trader; MLflow, DVC, and batch notebooks remain in 04-ml-workflow.

• skills/local/ — custom-authored skills.
  • project-knowledge-harness — TODO + backlog + pitfalls structure with init / kanban / promote / add-todo / sweep-inbox toolkit. (docs)
  • quantatitive-factor-researcher — Python quant-research persona. (docs)
  • vectorbt — OSS/PRO library development, XDG documentation sync, migration guidance, and optional official MCP setup. (docs)
  • nautilus-trader — NautilusTrader development: detects the v1 Cython vs v2 Rust/PyO3 generation, syncs version-matched docs/examples from git tags into an XDG cache, and gates sandbox/live trading. (docs)
  • skill-author — Author new skills following agentskills.io best practices; ships new-skill.sh scaffolder and lint-skill.sh linter. (docs)
  • — Design CLIs/tools/services with ///isolated-state smoke, and verify config/CLI/dotfile/IaC changes via app-native loaders before claiming done. ()

Categories in the install UI

The grouped picker UI of npx skills@latest add daviddwlee84/agent-skills/skills is driven by skills/.claude-plugin/marketplace.json. Each plugin entry defines one category and explicitly lists its member skills; anything not listed there falls under Other automatically. The manifest is the source of truth for the current category set rather than a duplicated list in this README.

# Validate the manifest (paths exist, no duplicates, name not reserved,
# on-disk skills covered).
make marketplace

# Exercise Claude Code + Codex native add/list/install in isolated state.
make native-marketplace-smoke

The manifest lives under skills/, not at the repo root, because the install command's /skills subpath makes the CLI read <repo>/skills/.claude-plugin/marketplace.json. See npx skills metadata model for the full mechanism, the kebabToTitle group naming rule, reserved marketplace names, and the marketplace.json vs plugin.json distinction.

Repo memory

This repo dogfoods project-knowledge-harness on itself:

• TODO.md — priority/effort-tagged backlog.
• backlog/ — research notes for P? items (when populated).
• backlog/inbox.md — quick-capture inbox; sweep into TODO.md later.
• pitfalls/ — symptom-grep-able knowledge base of past traps (when populated).

# Validate TODO.md and render kanban-style board
make kanban

# Quick add structured TODO entry
./scripts/add-todo.sh --priority P3 --effort M --title "..." --description "..."

# Move an active TODO to ## Done in same commit as the implementation
./scripts/promote-todo.sh --title "<substring>" --summary "<shipped summary>"

# Triage backlog/inbox.md interactively
./scripts/sweep-inbox.sh

Full workflow: Project memory.

Vendor system

# Add a vendored skill (auto-syncs)
./scripts/add-vendor.sh owner/repo/path/to/skill
# or via Makefile
make add-vendor SOURCE=owner/repo/path/to/skill

# Group into a series subdir (skills/vendor/<series>/<name>/)
./scripts/add-vendor.sh --series fullstack-nextjs vercel/vercel-plugin/skills/nextjs

# Sync all vendored skills from upstream
make sync

# Check for upstream updates (dry-run)
make sync-check

Full workflow: Adding vendor skills.

Dependencies: gh (GitHub CLI, authenticated) and yq (YAML processor).

Docs site

The docs site is built with MkDocs Material + mkdocs-llmstxt + mkdocs-copy-to-llm.

uv sync --extra docs
make docs-serve         # http://127.0.0.1:8000/
make docs-build         # produces ./site/

Deployed automatically to GitHub Pages on push to main via .github/workflows/docs.yml.

If you want to apply the same docs stack to your own project, see Downstream docs stack recipe.

Adding a new local skill

Use the bundled scaffolder (recommended — seeds the agentskills.io best-practice template and fans out discovery symlinks for non-universal agents):

# Auto-detects scope: LOCAL (this repo) / PROJECT (another git repo) / GLOBAL (~/).
bash skills/local/skill-author/scripts/new-skill.sh <skill-name>

# Override scope explicitly when intent isn't obvious:
bash skills/local/skill-author/scripts/new-skill.sh --project <skill-name>
bash skills/local/skill-author/scripts/new-skill.sh --global  <skill-name>

bash skills/local/skill-author/scripts/lint-skill.sh skills/local/<skill-name>

The scaffolder mirrors npx skills add's placement contract — canonical content goes under .agents/skills/<name>/ (read directly by Cursor / Codex / OpenCode / Warp / Gemini-CLI / Copilot), with relative symlinks fanned out to .claude/skills/ and any other already-present non-universal agent dir. In this repo (LOCAL mode) the canonical lives in skills/local/<name>/ and the symlinks point back at it. See Creating local skills for the full scope table.

Or, just the SKILL.md skeleton via the upstream init (no symlinks, no references/ / scripts/ / assets/):

cd skills/local
npx skills@latest init [skill-name]

Resources

The full curated index of upstream skill collections, MCP servers, and domain-specific hubs lives in the docs site:

📚 Catalog — external skill collections, per-domain hubs (Finance, Quant Research, AI/ML Research, Web & Fullstack, Knowledge Work, Agent Harness), a docs-only curiosity shelf, and an MCP wiki.

Highlights:

• Skill collections index — every upstream we track, with vendored / deferred / skipped / evaluated / wishlist status per entry.
• Skill curiosity shelf — unusual or playful skills worth remembering without adding them to normal discovery or workflows.
• Finance hub — covers anthropics/financial-services, RKiding/Awesome-finance-skills, the Financial Datasets MCP, and more.
• Adding catalog entries workflow — how to record an external skill / MCP / domain decision.