Skilldex-skillset

Guides you through designing and writing a new Claude skill from scratch — determines the right complexity tier, writes the SKILL.md with correct frontmatter and instructions, and scaffolds any supporting assets, references, or scripts the skill needs.

Guides you through designing and packaging a complete skillset — determines what skills belong together, writes the SKILLSET.md manifest, identifies shared assets, and produces the full directory layout with all skill files ready to install.

Generates structured competitor breakdowns from information you provide. Uses a bundled analysis framework to evaluate competitors across consistent dimensions — positioning, pricing, features, weaknesses, and moat — and outputs a formatted report ready to share with stakeholders or paste into a product document.

Produces structured summaries of academic or technical papers. Fills a consistent template covering abstract, key contributions, method, results, limitations, and relevance. Calibrates terminology and depth to a named audience using the shared audience personas reference — so the summary is useful to the right reader, not just accurate.

Explains complex technical topics in plain language calibrated to a named audience. Loads a shared audience personas reference to determine vocabulary level, assumed prior knowledge, and preferred explanation style — so the explanation lands for that specific reader, not for a generic one.

Produces CHANGELOG entries from git history following the Keep a Changelog format. Uses a bundled script to extract commits since the last tag, classifies them into changelog sections using the shared commit conventions reference, and outputs a ready-to-paste release block.

Writes well-formed commit messages following the Conventional Commits specification. Infers the commit type and scope from the staged diff and changed file paths, asks for clarification only when the intent is genuinely ambiguous, and formats the result ready to paste into your terminal.

Generates structured pull request descriptions from the staged diff and branch name. Fills in a standard PR template covering summary, what changed and why, testing steps, and any notes for reviewers — so you spend time on the code, not on writing boilerplate.

Writes tests that match your project's existing test patterns and conventions. Detects the test framework in use, reads nearby test files to understand naming and structure conventions, and generates tests for the code you point it at — without introducing a different style.