ai-literacy-superpowers

Run an AI literacy assessment — scan the repo for evidence, ask clarifying questions, produce a timestamped assessment document, apply immediate habitat fixes, recommend workflow changes, capture a reflection, and add a literacy level badge to the README

Run a guided convention extraction session — surfaces tacit team knowledge through structured questions and maps answers to CLAUDE.md conventions and HARNESS.md constraints

Run a full meta-verification of the harness — check whether HARNESS.md matches reality and update the status

Add a new constraint to HARNESS.md or promote an existing one from unverified to agent or deterministic

Manage and run garbage collection rules — add new periodic checks or run existing ones on demand

Generate a harness health snapshot — enforcement status, mutation trends, learning velocity, cadence compliance, and meta-observability checks

Set up a living harness for this project — discover the stack, define conventions, generate HARNESS.md with enforcement

Show the current health of the project's harness — enforcement ratio, drift, and garbage collection state

Capture a reflection after completing work — what was surprising, what should future agents know, what could improve

Set up the complete AI Literacy framework habitat for this project — discover the stack, define conventions, scaffold harness, agent team, compound learning, and CI templates

Show the complete health of the project's AI Literacy habitat — harness enforcement, agent team, compound learning, model routing, and CI status

Manage git worktrees for parallel agent isolation — spin up a new worktree, merge it back, or clean it up

You assess a team's AI collaboration literacy level by combining

Use after implementation is complete and tests are green — reviews code through the CUPID and literate programming lenses, returns PASS or a prioritised list of findings

You are the meta-agent for the harness framework. Your job is to check

You are a read-only project scanner. Your sole purpose is to observe

You are the unified verification engine for the harness framework.

You are the entropy fighter for the harness framework. You run periodic

Use when implementation and code review are complete — updates CHANGELOG, commits all changes, opens a PR, watches CI, merges when green, closes the linked issue, and prunes the local branch

Use when starting any new feature, fix, improvement, or refactoring task — receives a plain-English task description and coordinates the full pipeline from spec update through to merged PR and closed issue

Use when a feature, behaviour change, or improvement needs to be captured in a spec before implementation begins — updates spec and plan files so the project's spec-first discipline is upheld

Use after spec-writer has updated the spec and plan, and the user has approved the plan — writes failing tests that express the new acceptance scenarios, then confirms they are red before any implementation is written

This skill should be used when the user asks to "assess AI literacy", "run an assessment", "check literacy level", "evaluate our AI collaboration", "where are we on the framework", or wants to determine their team's AI literacy level using the ALCI instrument.

This skill should be used when the user asks to "add a constraint", "design a constraint", "write a harness rule", "choose enforcement type", "promote a constraint", "configure a verification slot", or needs guidance on the Constraints section of HARNESS.md.

This skill should be used when the user asks about "writing conventions", "codebase context", "HARNESS.md context section", "convention documentation", "how to write enforceable rules", or needs guidance on the Context section of HARNESS.md.

Use when setting up a new project's conventions, onboarding AI to an existing codebase, after team composition changes, or when AI output quality varies depending on who prompts — guides structured discovery of tacit team knowledge into explicit, enforceable artefacts

Use when coordinating changes across multiple repositories — syncing skills, templates, agents, or harness policies between upstream and downstream repos, or designing portfolio-level agent orchestration

Use when reviewing or refactoring code and wanting a structured lens beyond SOLID — applies Daniel Terhorst-North's CUPID properties to surface improvement opportunities in any codebase or language.

Use when auditing project dependencies for known vulnerabilities, supply chain risk, or provenance issues — covers Go modules, Maven/JVM, and CI integration for automated scanning

Use when auditing Docker images in this project for CVEs, base image staleness, or remediation recommendations — covers all four TUI images (Go, Python, Kotlin, C#)

This skill should be used when the user asks about "garbage collection rules", "entropy fighting", "documentation staleness", "dead code detection", "convention drift", "periodic checks", "auto-fix rules", or needs guidance on the Garbage Collection section of HARNESS.md.

Use when reviewing GitHub Actions workflow files for security issues, hardening CI pipelines, or assessing supply chain risk in a repository that uses GitHub Actions

This skill should be used when the user asks about "harness engineering", "what is a harness", "harness framework", "AI code quality", "context engineering", "architectural constraints", "garbage collection for code", or wants to understand the conceptual foundation behind the harness-engineering plugin.

Use when checking harness health, setting up observability cadences, understanding snapshot formats, configuring telemetry export, or verifying that the harness's own observability is working — covers all four layers of harness observability

Use when creating new source files, writing new functions or types, or significantly rewriting existing code — ensures code is structured for humans to read first, with narrative preambles, reasoning-based documentation, and presentation ordered by understanding rather than compiler convention

This skill should be used when the user asks about "verification slots", "integrating a linter", "adding a deterministic tool", "harness-enforcer", "constraint enforcement interface", "wrapping a tool", or needs the technical reference for how deterministic and agent-based checks work in the harness framework.

5 hooks across 2 events