permanu

Superskill — Testing skill for Claude Code

Testing community

One-entry orchestrator for coding agents: jailed vault, FTS knowledge graph, 18-axis review, in-harness Chrome QA.

How to install Superskill

This entry records only its repository, not the path inside it, so there is no exact command to give. Open permanu/superskill and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Superskill does

One-entry orchestrator for coding agents: jailed vault, FTS knowledge graph, 18-axis review, in-harness Chrome QA. Curated packs — not a 90k-skill dump.

Alternatives in Testing

  • Spec Kitty — Spec-Driven Development for serious software developers 1.6k ★
  • Spec Driven Develop — Spec-driven development workflow for AI coding agents: architecture-first planning, task decomposition, GitHub 975 ★
  • Claude Dev Skill — A Claude Code custom skill that turns Claude into a Tech Lead — coordinating parallel Worker Agents through a 112 ★

README

SuperSkill

One-entry orchestrator for coding agents. Curated packs, project-jailed vault, FTS knowledge graph. Not a dump of 90k remote skills.

[![npm](https://img.shields.io/npm/v/superskill)](https://www.npmjs.com/package/superskill) [![license](https://img.shields.io/badge/license-AGPL--3.0-blue)](https://www.gnu.org/licenses/agpl-3.0)

Prompt normally. Call **`superskill`** with the task. It diagnoses, then delegates (Go → Go pack, QA → QA, security bug → review + security). Defaults: ADHD-shaped output, careful-minimal, algorithm-correct, **systems thinking**. Review walks **18 axes**; open branches **grill the human** (HITL). Factory packs (plan, TDD, verify, SRE, grill) are **ours**.

Requires **Node 22+** (`node:sqlite`).

Why

Marketplace skill dumps fill the window with advice that does not know *this* system. Review and security need:

  • Vertical — this project’s ADRs, learnings, sessions
  • Horizontal — callers, sibling paths, co-activations
  • Fresh — session complete + learn

SuperSkill injects a system brief from the project graph, jails vault IO to `projects//`, and keeps `.superskill/` **gitignored** so each developer’s trajectory stays private.

How it works

  1. npx superskill-cli init — detect stack, index the in-repo catalog (not skills.sh)
  2. Describe the task
  3. Inverted-index router picks packs (language, phase, specialists)
  4. Content is budgeted. Real review/diff/audit (and security bugs) get the vault + caller protocol
  5. Activations write .superskill/graph.json (local only)

Packs

Pack When
pipeline/delivery + norms Always. Diagnose, then load a combination — not a 10-step ritual
optimizer/algorithm Always. Invariant, O(…), HLD/LLD that pay rent
memory/graph Always (tiny). This project’s vault only
security/index Tiny always-on. Full compliance on audit / OWASP / security bugs
code/ This repo’s stack, or the task names a langu