Skip to content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

54 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

@theholocron/skills

Shared agent skill registry.

Each skill is a directory under skills/ containing a SKILL.md file that Claude Code (and compatible agents) can load as a slash command.

Owned skills

Skills authored and maintained in this repo. Published inside the npm package.

Workflow & safety

Skill Description
git-safety Never force-push or run destructive git ops without permission
pr-workflow Always open a PR; one-change-per-PR; delete branch on close
commit-standards Conventional Commits format + DCO signing
security-review OWASP-oriented checklist for code review

Project-specific (theholocron)

Skill Description
holocron-skill-config Scaffold a new @theholocron/*-config package in theholocron/configs
holocron-skill-client Scaffold a new @theholocron/*-client package in theholocron/clients
holocron-skill-plugin Scaffold or migrate a new holocron-plugin-* package
holocron-skill-util Scaffold a new @theholocron/*-utils package in theholocron/utils
holocron-skill-skill Add a new owned skill to theholocron/skills

External skills

Tracked in skills-lock.json with source provenance and content hash. Not committed to this repo — fetched from upstream by holocron skills update (planned).

Skill Source Description
find-skills vercel-labs/skills Discover and install agent skills from the skills.sh ecosystem
frontend-design anthropics/skills Distinctive, intentional UI design guidance
vercel-cli vercel/vercel-plugin Vercel CLI: deploy, env vars, logs, domains, project linking
turbopack vercel/vercel-plugin Turbopack bundler: HMR, CSS, tree shaking, webpack migration
turborepo vercel/turbo Turborepo task pipeline configuration and cache optimization

Installation via holocron setup

Skills are installed by holocron setup based on the skills field in holocron.config.ts. They are written to .agents/skills/<name>/ with a symlink at the agent-specific path, and gitignored — treated as dependencies, not source.

// holocron.config.ts
import { defineConfig } from "@theholocron/cli";

export default defineConfig({
  agent: "claude",
  skills: ["git-safety", "pr-workflow", "commit-standards", "security-review"],
  // ...
});

Then run:

pnpm add -D @theholocron/skills
GITHUB_TOKEN=$(gh auth token) pnpm exec holocron setup

Manual installation

Copy a skill directory into your project's .agents/skills/ and symlink it:

cp -r node_modules/@theholocron/skills/skills/git-safety .agents/skills/
ln -s ../../.agents/skills/git-safety .claude/skills/git-safety

Add both to .gitignore:

# managed by holocron setup — skills
/.agents/skills/
/.claude/skills/git-safety

Contributing

Adding an owned skill

  1. Create skills/<name>/SKILL.md with the frontmatter format:
    ---
    name: <name>
    description: One-line description. INVOKE WHEN: <trigger conditions>.
    ---
    # skill title
  2. Run pnpm test — the smoke test checks that every skill dir has a SKILL.md.
  3. Update this README with a row in the owned skills table.
  4. Open a PR with a feat: commit — semantic-release handles versioning.

Registering an external skill

Run pnpm exec skills add <repo> --skill <name> from this repo root. This records the skill in skills-lock.json with its source and content hash but does not copy it into skills/ — external skill content is fetched at install time.

About

Shared agent skill registry.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Sponsor this project

Used by

Contributors

Languages