Loading…
Not enough history yet: 3 of 7 days recorded. Until then this list is ordered by the most recent content change.
77104 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| elaboration-upsert-prd-documenttsunami28/MindNovaWrite a Product Requirements Document for an initiative or epic - the problem, goals, scope, requirements, and success metrics - as the elaboration-phase anchor that stories derive from. Use when an initiative needs framing before it is sliced into work: phrasings like "write a PRD", "draft the product requirements", "what are the requirements for this epic", "spec out this initiative", "what's in and out of scope", "define success for MN-10", or when a confirmed hypothesis is ready to become a buildable epic. Do NOT use to capture an early hypothesis (that is discovery-upsert-hypothesis-canvas), to slice a PRD into stories (elaboration-upsert-user-story), to design the API contract (elaboration-upsert-api-contract), or to author an ADR (governance-author-adr). | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| elaboration-upsert-user-storytsunami28/MindNovaCreate or draft new work items (stories, tasks, bugs, epics) as local markdown files under docs/discovery/, following the house story template, point scale, and conventions. Use this whenever the user wants a new work item: phrasings like "create" or "write up a story", "make a ticket", "log a bug" or "ops task", "create an epic", "raise a ticket", or any description of work that should be tracked as a new item, even when they only describe the work rather than naming a ticket. Do NOT use this for reading, searching, commenting on, transitioning, or reviewing existing tickets; for GitHub issues or pull items, GitHub issues or pull requests, Confluence pages, or PRDs; or for a bare "what points would you give" estimate when there is no ticket to create. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| elaboration-upsert-user-story-acceptance-criteriatsunami28/MindNovaDerive clear, testable acceptance criteria for a story and define the test-trait mapping that lets the deferred AC-coverage gate attach with no rework. Use when the user says "write the acceptance criteria", "define the ACs for MN-42", "what are the success criteria for this story", "make these criteria testable", "turn this story into checkable conditions", or "set up the AC-to-test mapping" - and when a story is being refined for build but its success criteria are vague or untestable. Do NOT use to CREATE the story (that is elaboration-upsert-user-story), to implement or tag the tests (that is create-code-generation), or to write the work item fields directly (defer that to governance-enrich-ticket). | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| governance-author-adrtsunami28/MindNovaSuggest and author Architecture Decision Records (MADR-style) in docs/adrs/. Use when a load-bearing decision is being made or has just been made ("we decided to...", "let's go with X over Y", "should this be an ADR?", "record this decision", "write an ADR", "supersede ADR NNNN"), or when reviewing a plan/change that implies an unrecorded architectural choice. Also use to detect and flag decisions that ought to be recorded. Do NOT use for the project-wide constitution (that is the governance-constitution skill), for ordinary feature docs, or for tracker tickets. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| governance-check-graphtsunami28/MindNovaValidate documentation and graph integrity across the repo: the AI-SDLC artifact graph (every artifact declaring a `story:` has a valid work-item key, a known phase, and `relates:` links that resolve) AND the documentation wiki (no orphan pages, no broken relative links, indexes in sync), and documentation house-style (no em-dash characters). Use when the user says "check the artifact graph", "validate the artifact links", "lint the docs", "are the doc links broken", "check the wiki", "check for em-dashes", before opening a PR that touches docs or graph artifacts, or as the governance-check-graph step. It runs the same scripts the CI gates run, so local results match the pipeline. Do NOT use to create or fix artifacts, tickets, links, or docs (that is elaboration-upsert-user-story / governance-enrich-ticket / governance-author-adr / create-upsert-documentation). | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| governance-constitutiontsunami28/MindNovaCreate, amend, or check a project's governing "constitution" - the small set of non-negotiable engineering principles that every agent run (Claude Code and GitHub Copilot) should honour. Use when the user says "create/set up a constitution", "add a rule/principle to the constitution", "amend/update the constitution", "make this a non-negotiable", "what are our project principles", or asks to bootstrap the AGENTS.md contract; and in check mode when the user says "check my changes against the constitution", "does this violate a clause", "constitution check", or "review this for constitution compliance". Do NOT use for authoring a single architectural decision (that is governance-author-adr), for validating doc or graph link integrity (that is governance-check-graph), for ordinary docs, or for editing tracker tickets. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| governance-enrich-tickettsunami28/MindNovaUpdate an existing local work item (under docs/discovery/) so its content reflects current reality after work ships or scope changes: splice shipped behavior, decisions, and approach into the matching section, fix a stale title, add related-item links with the reason for each, and backlink ADRs, designs, and docs. Use when the user says "add this to MN-42", "enrich MN-42", "the ticket should say what we actually shipped", "update the description to match reality", "link these items and say why", "record this decision on the story", or finishes work that changed what the story is or produced an artifact worth recording. Invoking it is a directive to WRITE the file after one confirmation, not to leave a proposal. Do NOT use to CREATE a work item (that is elaboration-upsert-user-story) or to read or search items. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| governance-validate-skillstsunami28/MindNovaValidate the AI-SDLC skills under .claude/skills/ with the layered eval harness before relying on a new or changed one. Use when a skill has just been added or edited and needs checking, or when the user says "eval the skills", "validate this skill", "run the skill harness", "test the skills", "did my skill change break routing", or "check skill discriminability". This is the durable form of the "draft-only eval harness" the roadmap refers to. Do NOT use to validate the artifact graph or docs wiki (that is governance-check-graph), or to author or edit a skill's content. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| mature-analyze-tickettsunami28/MindNovaTriage an incoming work item (under docs/discovery/) - a bug report, request, or incident - so it is correctly understood, classified, and routed before anyone builds. Use when the user says "triage MN-42", "is this a real bug?", "can you reproduce this?", "what priority is this", "is this a duplicate", "look into this report/incident", or hands you an inbound item to assess. Reads the item and its evidence, reproduces or characterises the problem, classifies and prioritises it, checks for duplicates, and records a triage note. Do NOT use to CREATE an item (that is elaboration-upsert-user-story), to rewrite an item's content (that is governance-enrich-ticket), or to implement the fix (that is mature-resolve-ticket). | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| mature-collect-release-feedbacktsunami28/MindNovaGather post-release signals and record them as concise feedback notes anchored on the originating epic/story. Use after a release ships and you need to learn whether it delivered its intended outcome: phrasings like "did the release land", "collect feedback on what we shipped", "what is the telemetry showing for this feature", "summarise the support tickets since release", "what did stakeholders say", or when a feature is in production and should feed the next loop. This is the entry point to the mature phase. Do NOT use to triage a specific issue the feedback surfaced (that is mature-analyze-ticket), to turn validated needs into new stories (that is elaboration-upsert-user-story), to run fresh research (that is discovery-synthesize-research), or to add links to an already-recorded ticket (governance-enrich-ticket). | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| mature-resolve-tickettsunami28/MindNovaResolve a confirmed defect surfaced in the mature phase by running a scoped pass of the development cycle. Use when a triaged work item is a reproducible bug ready to fix: phrasings like "fix MN-42", "this defect is confirmed, go fix it", "resolve the bug from triage", "take this confirmed defect through the dev cycle", or when mature-analyze-ticket has handed off a confirmed reproduction. This is a thin entry point that frames the defect and delegates. Do NOT use to triage or confirm an issue first (that is mature-analyze-ticket), to build a new feature or make an ad-hoc code fix with no triaged ticket (use create-code-generation directly), or for a pure structural cleanup with no behaviour change (that is create-refactoring). | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| run-sdlctsunami28/MindNovaNavigate the AI-SDLC workflow for a given work item or artifact: report where it is in the lifecycle and what to do next. Use when the user asks "where are we on MN-42", "what is the next step for this story", "run the sdlc on <key or path>", "what is missing before this can ship", "which phase is this in", or hands over an artifact (a work item key, a spec, a doc, an ADR) and asks how to proceed. It is READ-ONLY for navigation: it resolves the anchor, traverses the artifact graph, and reports the current phase plus the next /<phase>-<step> and the persona who owns it. It does NOT create, edit, link, or transition anything, and it never writes directly; on explicit request it can dispatch the next step by handing off to the owning phase-step skill (which writes behind its own confirmation gates), per docs/ai-sdlc/orchestration.md. Do NOT use to author artifacts or to write work items. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| agent-change-gateCHENG-LIANG1/badass-skillsReview and gate AI-generated code changes by reconstructing intent, mapping diff risk, selecting independent verification, checking security and dependency impact, and requiring evidence before merge or release. Use for coding-agent pull requests, autonomous patches, or large AI-generated diffs; do not use for ordinary implementation requests or style-only review. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| agent-eval-contractCHENG-LIANG1/badass-skillsDesign trustworthy, reproducible evaluations for AI agents, skills, prompts, and tool loops by turning quality claims into scenarios, evidence, baselines, validity checks, and ship gates. Use for version comparisons, regression detection, or release decisions; do not use for ordinary deterministic unit tests. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| agent-harness-auditorCHENG-LIANG1/badass-skillsAudit or improve a code repository's AI-agent harness by making project knowledge discoverable, commands reproducible, architectural invariants executable, and feedback loops fast. Use when preparing a codebase for Codex or other coding agents, investigating inconsistent agent changes, or reviewing AGENTS.md and repository guidance; do not use for ordinary code review or a one-off task with no repository-level issue. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| agentic-workflow-contractCHENG-LIANG1/badass-skillsDesign safe, repeatable agentic automations for scheduled or event-driven work by defining triggers, permissions, idempotency, budgets, review gates, failure handling, and observable proof. Use when creating or reviewing recurring AI-agent workflows, Codex automations, or GitHub Agentic Workflows; do not use for one-off agent tasks or deterministic jobs better handled by a normal script. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| blast-radius-guardCHENG-LIANG1/badass-skillsPreflight consequential agent actions by resolving exact targets, authority, reversibility, retry ambiguity, rollback, and independent verification. Use before destructive, externally visible, bulk, financial, permission, deployment, send, or publish operations; do not use for read-only work or trivial reversible local edits. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| context-architectCHENG-LIANG1/badass-skillsStructure long-running, multi-file, or handoff-prone work into a compact evidence-linked context that survives compaction and agent transitions. Use when a task spans multiple phases, sources, decisions, or sessions; do not use for short self-contained requests. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| failure-forensicsCHENG-LIANG1/badass-skillsDiagnose reproducible or intermittent failures in tests, builds, CI, dev servers, CLIs, and integrations by turning symptoms into falsifiable hypotheses and small discriminating experiments. Use when the root cause is unknown; do not use for a routine fix whose cause is already established. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| instruction-provenance-guardCHENG-LIANG1/badass-skillsProtect AI-agent tasks from indirect prompt injection and untrusted tool output by tracing instruction provenance, separating data from authority, constraining source-to-sink flows, and confirming sensitive disclosure or action. Use when reading webpages, issues, emails, documents, logs, MCP results, or third-party skills while tools can access private data or mutate state; do not use for ordinary trusted inputs with no external-content boundary. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| multi-agent-conductorCHENG-LIANG1/badass-skillsCoordinate multi-agent or subagent work by deciding when delegation helps, partitioning dependencies, assigning exclusive ownership, defining handoff artifacts, and verifying one integrated result. Use only when the user or applicable instructions explicitly request delegation, subagents, or parallel agent work; do not use for ordinary single-agent tasks. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| blogwatcher-cliHyaxia/blogwatcherUse when managing or interacting with favorite blogs via the BlogWatcher CLI—adding/removing blogs, scanning for new posts, listing articles, marking read/unread, or modifying related CLI behavior, scanning, storage, and tests. | Stars: 149 | Updated | Claude CodeCodex | Verified | Install |
| blogwatcherHyaxia/blogwatcherMonitor blogs and RSS/Atom feeds for updates using the blogwatcher CLI. | Stars: 149 | Updated | Claude CodeCodex | Verified | Install |
| apple-designyerzong/TEMP-LEAGUECross-platform UI/UX design reviewer grounded in Apple Human Interface Guidelines principles. Use this skill to audit, review, critique, or improve any UI/UX design for mobile apps (iOS, Flutter, React Native) or desktop apps (macOS, Tauri, Electron). Triggers when the user mentions: design review, UI audit, HIG compliance, improving app design, design feedback, accessibility audit, or any request to check or improve a design against professional standards. Also use when the user uploads screenshots, mockups, wireframes, or design specs of a mobile or desktop app and wants feedback. Even if they just say "review my design" or "is this good UI", use this skill. Works for native and cross-platform frameworks including Flutter, Tauri, Electron, React Native, SwiftUI, and AppKit/UIKit. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| apple-hig-designeryerzong/TEMP-LEAGUEDesign Apple-style iOS/macOS/visionOS interfaces following Human Interface Guidelines. Creates HIG-compliant components with SF Symbols, San Francisco typography, system colors, proper accessibility, and platform-appropriate patterns. Supports Liquid Glass (iOS 26+), adaptive layouts, and multi-platform design. Use this skill whenever the user asks for Apple-style UI, iOS/macOS/watchOS/tvOS/visionOS interfaces, HIG-compliant components, SF Symbols integration, or anything involving Apple design language — even if they just say "make it look like an iPhone app" or "native iOS feel". Also trigger for requests involving widgets, notifications, Live Activities, onboarding flows, settings pages, or navigation patterns in an Apple context. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| apply-design-systemyerzong/TEMP-LEAGUEReview an existing design and connect it to design system components. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| audit-design-systemyerzong/TEMP-LEAGUEAudit a Figma screen or component for design-system integration drift, including missing shared components, local overrides, and unbound tokens. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| design-reviewyerzong/TEMP-LEAGUERevisa una propuesta de UI/UX de Temp League contra el design brain, los tokens y las reglas de producto. Úsalo cuando alguien pida "revisa este diseño", "design review", validar una pantalla/componente, o antes de dar por terminada una propuesta visual. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| fix-design-system-findingyerzong/TEMP-LEAGUEFix a specific design-system integration finding in a Figma screen or component, including missing shared components, local overrides, and unbound tokens. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| sync-figma-tokenyerzong/TEMP-LEAGUESync design tokens between code and Figma variables with strict drift reporting, mandatory approval gate, safe delta apply, and persisted reports. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |