All authors
Claude Skills by Habitat-Thinking
github.com/Habitat-Thinking45 skills0 installs94 views
- Advocatus DiaboliUse when acting as the adversarial spec reviewer — raises steel-manned objections across six categories before plan approval, requires evidence per objection, and discloses what was not challengedVotes: 0GitHub stars: 104
- Ai Literacy AssessmentThis 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.Votes: 0GitHub stars: 104
- Auto Enforcer ActionUse when setting up automatic PR constraint enforcement via GitHub Actions — covers the advisory-vs-blocking split, workflow installation, configuration options, and reading the outputVotes: 0GitHub stars: 104
- Choice CartographerUse when acting as the decision-archaeology agent — surfaces decisions a spec has made (including the silent ones), emits each material choice as a Henney-style pattern story for human disposition, and pays down intent debt before plan approvalVotes: 0GitHub stars: 104
- Component Design With TdadUse when designing a new plugin component (skill, agent, command, or backing script) for the ai-literacy-superpowers plugin or a sister plugin in this marketplace. Surfaces the design questions that the four-layer TDAD architecture implies — component type, tier targeting, scenario shape, FINDING-vs-scenario judgement, modification-vs-refactor heuristic. Loadable by spec-writer, tdd-agent, or directly during human brainstorming. Not a gate; a methodology guide that names the questions to ask ...Votes: 0GitHub stars: 104
- Constraint DesignThis 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.Votes: 0GitHub stars: 104
- Context EngineeringThis 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.Votes: 0GitHub stars: 104
- Convention ExtractionUse 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 artefactsVotes: 0GitHub stars: 104
- Convention SyncUse when syncing HARNESS.md conventions to Cursor, Copilot, and Windsurf convention files — reads Context and Constraints sections and generates tool-specific output so all AI coding tools share the same project rulesVotes: 0GitHub stars: 104
- Cost TrackingUse when the user wants to capture AI tool costs, review spending trends, set cost budgets, or integrate cost data into health snapshots — guides quarterly cost capture, records data in a structured format, and updates MODEL_ROUTING.md with observed cost patternsVotes: 0GitHub stars: 104
- Cross Repo OrchestrationUse when coordinating changes across multiple repositories — syncing skills, templates, agents, or harness policies between upstream and downstream repos, or designing portfolio-level agent orchestrationVotes: 0GitHub stars: 104
- Cupid Code ReviewUse 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.Votes: 0GitHub stars: 104
- Dependency Vulnerability AuditUse when auditing project dependencies for known vulnerabilities, supply chain risk, or provenance issues — covers Go modules, Maven/JVM, and CI integration for automated scanningVotes: 0GitHub stars: 104
- Docker Scout AuditUse when auditing Docker images in this project for CVEs, base image staleness, or remediation recommendations — covers all four TUI images (Go, Python, Kotlin, C#)Votes: 0GitHub stars: 104
- Fitness FunctionsUse when designing architectural fitness functions as GC rules — periodic checks that verify system-wide properties like layer boundaries, coupling trends, and complexity hotspots, complementing per-change constraints with weekly architectural health monitoringVotes: 0GitHub stars: 104
- Garbage CollectionThis 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.Votes: 0GitHub stars: 104
- Github Actions Supply ChainUse when reviewing GitHub Actions workflow files for security issues, hardening CI pipelines, or assessing supply chain risk in a repository that uses GitHub ActionsVotes: 0GitHub stars: 104
- Governance Audit PracticeUse when conducting a governance audit — detecting semantic drift in governance constraints, inventorying governance debt, checking three-frame alignment, or when the governance-auditor agent needs methodology for deep investigation.Votes: 0GitHub stars: 104
- Governance Constraint DesignUse when writing governance constraints for HARNESS.md, translating governance language into operational meaning, reviewing existing governance constraints for falsifiability, or when "/governance-constrain" needs guidance on the authoring workflow.Votes: 0GitHub stars: 104
- Governance ObservabilityUse when defining governance metrics, reading governance health snapshots, generating the governance dashboard, or understanding the governance data model. Referenced by the governance-auditor agent and the /governance-health command.Votes: 0GitHub stars: 104
- Harness Audit EngineUse when running the shared drift-detection logic that backs /harness-audit and /harness-sync — produces a structured drift report covering convention files, ONBOARDING.md, snapshot staleness, template drift, constraint regressions, recurring reflection patterns, and HARNESS.md Status section accuracy.Votes: 0GitHub stars: 104
- Harness EngineeringThis 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.Votes: 0GitHub stars: 104
- Harness ObservabilityUse 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 observabilityVotes: 0GitHub stars: 104
- Harness OnboardingUse when generating a human-readable onboarding document from HARNESS.md, AGENTS.md, and REFLECTION_LOG.md — produces a friendly guide for new team members joining a harnessed projectVotes: 0GitHub stars: 104
- Literacy ImprovementsUse when generating a prioritised improvement plan after an AI literacy assessment, or when a user knows their current level and wants to know what to do next — maps gaps to specific plugin commands and skills, grouped by target level, with accept/skip/defer for each itemVotes: 0GitHub stars: 104
- Literate ProgrammingUse 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 conventionVotes: 0GitHub stars: 104
- Model SovereigntyThis skill should be used when the user asks about "local models", "custom models", "fine-tuning", "self-hosting models", "model selection", "which model should I use", "data privacy and models", "LoRA", "RAG vs fine-tuning", "Ollama", "vLLM", or wants guidance on whether to build, host, or customise their own AI models.Votes: 0GitHub stars: 104
- Portfolio AssessmentUse when assessing AI literacy across multiple repositories — aggregates individual assessments into a portfolio view with level distribution, shared gaps, outliers, and a prioritised improvement plan grouped by organisational impact. Discovers repos from local paths, GitHub orgs, or topic tags.Votes: 0GitHub stars: 104
- Portfolio DashboardUse when the user wants to generate, update, or customise an HTML dashboard from portfolio assessment data — produces a self-contained HTML file with level distribution, repo table, shared gaps, improvement plan, and trend visualisation from multiple quarterly assessmentsVotes: 0GitHub stars: 104
- Secrets DetectionUse when auditing a project for secrets committed to source control, setting up gitleaks, or hardening the "No secrets in source" harness constraint — covers scanning, baselining, configuration, and CI integrationVotes: 0GitHub stars: 104
- Team ApiUse when the user wants to create or update a Team Topologies Team API document with AI literacy portfolio assessment data — generates a template Team API with literacy levels, discipline scores, shared gaps, and improvement plans, or updates an existing Team API with the latest assessment dataVotes: 0GitHub stars: 104
- Verification SlotsThis 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.Votes: 0GitHub stars: 104
- TutorialsA skill is a Markdown file that agents read when working. It encodes knowledge your team has — domain rules, recurring corrections, project patterns — in a form that any Claude Code agent can act on. Skills are the difference between an agent that writes code that looks reasonable and one that writes code that fits your project. This tutorial walks you through creating a custom project-local skill, from identifying what to encode to writing the file and verifying the skill is active. It takes...Votes: 0GitHub stars: 104
- Model CardsUse when authoring or interpreting Mitchell-extended model cards in this plugin. Covers when each of the 10 sections applies, the citation discipline, the honesty rules (claim-level and card-level), and the tiered source strategy. Reference for the model-card-researcher agent and the /model-card command.Votes: 0GitHub stars: 104
- CarpaccioUse when acting as the cadence governor — slices a raw task description into thin, end-to-end-complete pieces before any spec is written; produces a structured slicing record for human disposition; runs at orchestrator step 0Votes: 0GitHub stars: 104
- CodaUse when closing an agentic session deliberately rather than by attrition — carries the four-step ritual (survey, park, closure summary and reflection, close), the anchor grammar behind the next-action question, the evidence for why a specific written plan releases an unfinished thread, and the anti-patterns that would turn a closing ritual into a gate on the personVotes: 0GitHub stars: 104
- Cognitive ReservoirUse when watching the human verifier rather than the output — defines the observable proxies, the observed/inferred/asked confidence discipline, the default thresholds, the one firm principle, six-level scaling, and the honesty rule that the reservoir-warden agent and the reservoir-check Stop hook both inheritVotes: 0GitHub stars: 104
- ConvenerUse when mapping the voices a spec affects and drafting the concrete question worth asking each one — the charter, the line the agent never crosses, where voices come from, what makes a question worth asking rather than a meeting worth scheduling, the three-way Routing Rule, and the consultation-record formatVotes: 0GitHub stars: 104
- Cost EstimationUse when the user wants to estimate or predict the cost, token usage, or time of a task BEFORE it runs — "how much will this feature cost to build", "estimate the tokens for this spec", "what will this slice cost", "predict the agent-compute time before I commit" — produces a token + time estimate as a range with disclosed confidence, adding a dollar figure only when an observability/costs snapshot grounds it. The prospective sibling of cost-tracking, which records actual spend after the fact.Votes: 0GitHub stars: 104
- Dynamic WorkflowsThis skill should be used when an agent is deciding whether to author a dynamic workflow — a self-authored, ephemeral multi-agent harness — for a task. Use when the user asks about "dynamic workflows", "multi-agent harness", "fan-out", "subagents in parallel", "adversarial verification", "the ultracode trigger", "should I use a workflow", or when a task looks long-running, massively parallel, highly structured, or adversarial. Names the six composable patterns, the election rubric for when NO...Votes: 0GitHub stars: 104
- MastUse when reading or authoring a self-declared pact — carries the two modes, the clear-weather rule and the exact blind spot of the check that enforces it, the flag discipline for a budget whose keys are mostly unobservable, the rules the pact writer guarantees, and the anti-patterns that would turn a pact-keeper into a gateVotes: 0GitHub stars: 104
- Sentinel DesignUse when designing, reviewing, or classifying an agent that guards the human — defines the sentinel category, the three-part signature (S1 read-only, S2 advisory-to-human, S3 explicit honesty rule), the near-miss gallery that explains why read-only-plus-advisory is not sufficient, the honesty-rule-before-detection-logic discipline, and the three anti-patterns that eject an agent from the categoryVotes: 0GitHub stars: 104
- Wip WardenUse when working on session-concurrency reporting — carries the constitutional boundary between counting sessions and watching the human, why that split protects the Reservoir Warden's trust model, the honest meaning of enforcement strict when no hook can hold a session, the flag discipline for an inexact count, and the anti-patternsVotes: 0GitHub stars: 104
- Plans> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking. **Goal:** Ship S1 of the cost-estimator capability — the `cost-estimation` skill, the estimate-record format reference, and a TDAD scenario for the skill. This slice ships the methodology and the format contract that S2–S6 consume. No agent, no command, no orchestrator wiri...Votes: 0GitHub stars: 104
- Active- **Date**: 2026-05-10 - **Agent**: claude-opus-4-7[1m] main session; no subagent dispatches - **Task**: Added `component-design-with-tdad` skill (issue #313) — methodology guidance loadable by `spec-writer`, `tdd-agent`, or human brainstorming when designing a new plugin component. Names the five design questions implied by the four-layer TDAD architecture: component type, layer targeting, scenario `Then` shape, new-vs-modification, scenario-vs-finding. Loadable rather than dispatchable — no...Votes: 0GitHub stars: 104