SkillFlux

    ↑ ↓ select↵ openSearch all of SkillFlux
    Browse directory
    Aspectgstack (Garry Tan)Superpowers (obra)
    Main purposeA role-based engineering team in Claude CodePlanning, debugging and testing workflows
    Source typeOpen-source repos · Open-source skill repositoryOpen-source repos · Open-source skill repository
    Use casesCoding & development, Testing & QA, Planning & long tasksCoding & development, Planning & long tasks, Security & review
    LanguageEnglishEnglish
    PricingFreeFree
    Best forBuilders who want an opinionated end-to-end workflow.Teams bringing planning, debugging and testing into a shared development process. Developers willing to read the framework’s rules and adapt them to a project.
    LimitationsOpinionated workflow; fit depends on your process.Framework rules may overlap with project conventions and need to be reconciled before adoption. Testing and review instructions are not themselves test results or security conclusions.
    SkillFlux sample5% clean · 0/20 fail at least one check · 19/20 do not say when to use the skill · 0/20 have no license we could find100% clean · 0/15 fail at least one check · 0/15 do not say when to use the skill · 0/15 have no license we could find

    gstack (Garry Tan): SkillFlux note

    Adopt one role at a time, for example review or QA, before using the whole flow.

    Visit gstack (Garry Tan) ↗

    Superpowers (obra): SkillFlux note

    Start with a change covered by existing tests and inspect the output of each step from planning to verification. The process should serve the project’s acceptance criteria. Explain adjustments where a step does not fit; completing a process is not proof that the feature works.

    Visit Superpowers (obra) ↗

    "Clean" is the share of sampled entries with no failing check, a "when to use" description and a license. Sampling reads files only and does not show whether a skill works. Method