SkillFlux

    ↑ ↓ select↵ openSearch all of SkillFlux
    Browse directory

    This page provides source information and editorial guidance. Recommendations and trust labels do not mean every skill here was tested. Results for individual skills are on the skill data pages. See skill data · Listing policy

    Overview

    Matt Pocock’s collection breaks development collaboration into composable steps: resolve open decisions, write a specification, divide work into verifiable tasks, then review coding standards and specification compliance separately. SkillFlux has collected all 38 skills at a pinned commit. This analysis explains the engineering workflow from its instructions so readers can choose the steps their project needs.

    SkillFlux sample check

    On 2026-10-31, SkillFlux pinned this source at commit a496f55, drew a seeded sample of 20 from the 38 entries it contains, and ran static health check 1.0.0 on each. 40% had no failing check, said when to use the skill and carried a license.

    • 20/20sampled entries had a SKILL.md we could check
    • 0/20fail at least one check
    • 12/20do not say when to use the skill
    • 0/20have no license we could find
    • 2/20bundle scripts the agent may run
    • 0/20include scripts that call the network
    • 0/20include destructive shell commands
    • 0/20exceed the 5,000-token body guideline
    See the 20 sampled entries
    EntryResultFlags
    mattpocock/skills/skills/engineering/wayfinder13 pass, 2 warn, 0 fail—
    mattpocock/skills/skills/misc/git-guardrails-claude-code15 pass, 0 warn, 0 failBundles scripts the agent may run
    mattpocock/skills/skills/engineering/research15 pass, 0 warn, 0 fail—
    mattpocock/skills/skills/misc/migrate-to-shoehorn15 pass, 0 warn, 0 fail—
    mattpocock/skills/skills/engineering/implement14 pass, 1 warn, 0 fail—
    mattpocock/skills/skills/productivity/grilling15 pass, 0 warn, 0 fail—
    mattpocock/skills/skills/engineering/codebase-design15 pass, 0 warn, 0 fail—
    mattpocock/skills/skills/engineering/retro13 pass, 2 warn, 0 fail—
    mattpocock/skills/skills/in-progress/writing-shape14 pass, 1 warn, 0 fail—
    mattpocock/skills/skills/engineering/to-spec14 pass, 1 warn, 0 fail—
    mattpocock/skills/skills/engineering/wizard15 pass, 0 warn, 0 failBundles scripts the agent may run
    mattpocock/skills/skills/engineering/improve-codebase-architecture14 pass, 1 warn, 0 fail—
    mattpocock/skills/skills/in-progress/writing-fragments14 pass, 1 warn, 0 fail—
    mattpocock/skills/skills/productivity/to-questionnaire14 pass, 1 warn, 0 fail—
    mattpocock/skills/skills/productivity/grill-me14 pass, 1 warn, 0 fail—
    mattpocock/skills/skills/in-progress/claude-handoff14 pass, 1 warn, 0 fail—
    mattpocock/skills/skills/in-progress/writing-beats14 pass, 1 warn, 0 fail—
    mattpocock/skills/skills/engineering/prototype15 pass, 0 warn, 0 fail—
    mattpocock/skills/skills/engineering/code-review15 pass, 0 warn, 0 fail—
    mattpocock/skills/skills/engineering/implement-spec14 pass, 1 warn, 0 fail—

    The sample reads files only; it does not run any skill and does not describe entries outside the sample. Flags describe what a skill contains; they are not verdicts. Raw data · Method

    What the skills help you do

    Inputs, methods and outputs described in the collected source version.

    Interview by decision dependencies

    grilling maps an idea into a decision tree. Each round asks only questions whose prerequisites are settled and offers recommendations, avoiding downstream design based on unresolved assumptions.

    Read the source instructions ↗

    Synthesize a specification

    to-spec synthesizes the conversation and codebase into a problem statement, user stories, implementation decisions, testing boundaries and exclusions for handoff after clarification.

    Read the source instructions ↗

    Divide a specification into verifiable tasks

    to-tickets creates small vertical slices across data, interfaces, UI and tests, with explicit blocking dependencies. Each completed ticket should be independently demonstrable or verifiable.

    Read the source instructions ↗

    Separate standards and specification reviews

    code-review starts from a fixed Git comparison point and separately checks repository standards and the originating specification, so clean code does not hide missing requirements.

    Read the source instructions ↗

    A typical workflow

    1. Choose the current step

      Start with an unresolved idea, discussed requirements or an existing specification. Check the selected skill’s trigger and host dependencies.

    2. Set requirements and acceptance boundaries

      Resolve decision dependencies when an interview is needed, then use to-spec to record user stories, testing boundaries and exclusions.

    3. Work through task dependencies

      Use to-tickets to divide work into verifiable vertical slices. During implementation, advance tasks with completed prerequisites and retain validation results.

    4. Review against specifications and standards

      Review changes against a fixed Git comparison point, record specification gaps and standards issues separately, then prepare the handoff.

    Best for

    • Developers who need to clarify hidden assumptions, acceptance criteria and project vocabulary before implementation.
    • Teams with specifications or tickets that want to implement in dependency order and distinguish coding standards from requirement coverage.

    Use cases

    SkillFlux notes

    This page analyzes the instructions, references and scripts of the 38 skills at a pinned commit, across engineering, productivity, misc and in-progress; it does not claim execution testing of these workflows. Listed skills each have a health check report; install them by following the original repository.

    Installation and use

    Open the original repository and read its README, the selected skill instructions and any linked scripts. Check installation paths, host requirements, dependencies and licenses, then follow the project documentation to verify a small task in a workspace you can restore.

    Read the original mattpocock/skills source

    Limitations

    • Some workflows require a configured issue tracker, domain glossary and architecture decisions. Implementation and review may also depend on other skills, Git and subagents.
    • Interviews, specification publication and ticket approval have different interaction boundaries. The 38 skills are not one program that completes development in a single call; in-progress also contains workflows under development upstream.

    Alternatives

    Related entries4 sources

    VoltAgent’s awesome-agent-skills brings vendor-team and community skill sources together in a curated GitHub list. Its scope is broader than a single agent, making it useful for comparing source types before checking each project’s host requirements, installation method and capability scope.

    SkillsOpen-source reposOpen sourceGitHubGlobal
    View

    Composio’s awesome-claude-skills is a curated Claude Skills list on GitHub that organizes candidate resources by topic. It is useful for surveying capability areas and then following links to the projects that provide the implementations.

    SkillsOpen-source reposOpen sourceGitHubGlobal
    View

    A web-based directory of agent plugins from official and community providers, rebuilt daily, where you can assemble a stack and install it with one script. The site is published on GitHub Pages.

    Skills + PluginsOpen-source reposGitHubOpen sourceGlobal
    View

    A library of installable SKILL.md playbooks for Claude Code, Codex, Cursor, Gemini CLI and others, with AAS Core to search the local catalog, record chosen skills and preview a plan before changing a project. The README says Core does not rank or recommend skills.

    SkillsOpen-source reposGitHubOpen sourceGlobal
    View