jburns personal skills

Personal agent skills collection for the agentskills platform.

Quick Start

Install all skills:

npx skills add jburns24/skills --all

Install a specific skill:

npx skills add jburns24/skills --skill <name>

Skills

Structure

skills/
  commit/              # Commit skill
    SKILL.md
  find-commit/         # Find-commit skill
    SKILL.md
template/
  SKILL.md             # Boilerplate for new skills
.claude-plugin/
  marketplace.json     # Plugin bundle config

Remote skill catalog

catalog.yaml (repo root) is a human-readable manifest of remote agent skills that live in other GitHub repos and can later be vendored into skills/<name>/. It is the single source of truth — each entry pins a resolved commit sha so references stay reproducible.

Manage it with scripts/catalog.py (uses PyYAML and the gh CLI):

# Add a skill (resolves the ref → SHA via gh, then appends an entry)
uv run scripts/catalog.py add anthropics/skills --path skills/mcp-builder --ref main

uv run scripts/catalog.py list                 # aligned table (--json for machine output)
uv run scripts/catalog.py show mcp-builder      # full details for one entry
uv run scripts/catalog.py update mcp-builder    # re-resolve ref → latest SHA (--all for every entry)
uv run scripts/catalog.py edit mcp-builder --depends other-skill  # edit description/depends, no SHA change
uv run scripts/catalog.py remove mcp-builder    # delete an entry
uv run scripts/catalog.py validate              # schema check (non-zero exit on failure; CI-friendly)

Each entry requires name (the unique primary key), repo (owner/repo), path, ref, and sha; description, depends, and updated are optional. Actual vendoring/copying is out of scope for this tool.

depends is a list of other catalog names a skill references (e.g. "install X before this one"). It's informational only — every entry vendors independently regardless of order, so there is no build-time resolution. validate checks that every referenced name exists in the catalog and that no dependency cycle exists.

Annotated example entry:

- name: some-skill          # local name → maps to skills/<name>/ when vendored
  repo: owner/repo          # source GitHub repo
  path: skills/some-skill   # subpath of the skill within the source repo
  ref: main                 # requested branch/tag/ref
  sha: 1a2b3c4...           # resolved commit SHA (full 40-char, pinned)
  description: "short note"  # optional
  depends: [other-skill]      # optional, names of catalog skills this one references
  updated: "2026-07-23T00:00:00Z"  # optional, set when sha was last resolved

Note: catalog.yaml is machine-managed — tool writes round-trip through PyYAML and strip all comments, so keep field documentation here rather than inline in the manifest.

Platform

• Spec: https://agentskills.io/specification
• GitHub reference: https://github.com/anthropics/skills

{
  "name": "jburns-personal-skills",
  "owner": {
    "name": "jburns"
  },
  "metadata": {
    "description": "Personal agent skills collection",
    "version": "1.0.0"
  },
  "plugins": [
    {
      "name": "personal-skills",
      "description": "jburns personal skill collection",
      "source": "./",
      "strict": false,
      "skills": [
        "./skills/commit",
        "./skills/find-commit",
        "./skills/prd-arena"
      ]
    }
  ]
}