jackonedev/agent_skills
Skill Claude CodeCodex
Creates and updates AGENTS.md files (repo root and subfolder/component). Provides copy-paste templates and ensures Auto-invoke sections stay syncable. Trigger: When the user asks to create/update an AGENTS.md, wants an AGENTS.md template, or is setting up root vs component agent instructions.
jackonedev/agent_skills
Skill Claude CodeCodex
Creates and updates CHANGELOG.md files with consistent structure and entries. Trigger: When adding a changelog entry for a PR/feature, updating any CHANGELOG.md, or creating a release section.
jackonedev/agent_skills
Skill Claude CodeCodex
Your pathfinder for navigating unknown codebases. Investigates with precision, implements surgically, and never assumes — if it doesn't know, it says so. Maintains a .notebook/ knowledge base that grows across sessions, turning every discovery into lasting intelligence. Summons available skills, MCPs, and docs when…
jackonedev/agent_skills
Skill Claude CodeCodex
Behavioral guidelines to reduce common LLM coding mistakes when writing, modifying, or reviewing code. Trigger: Apply on implementation tasks, code changes, refactoring, bug fixes, or feature development.
jackonedev/agent_skills
Skill Claude CodeCodex
As an expert technical writter and editor, your goal is to produce and refine documentation that is accurate, clear, consistent, and easy for users to understand. You must adhere to the documentation contribution process outlined in CONTRIBUTING.md.
jackonedev/agent_skills
Skill Claude CodeCodex
Creates new AI agent skills following the Agent Skills spec. Trigger: When user asks to create a new skill, add agent instructions, or document patterns for AI.
jackonedev/agent_skills
Skill Claude CodeCodex
Syncs skill metadata to AGENTS.md Auto-invoke sections. Trigger: When updating skill metadata (metadata.scope/metadata.autoinvoke), regenerating Auto-invoke tables, or running ./skills/skill-sync/assets/sync.sh (including --dry-run/--scope).
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: