Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 60091–60120 of 60980 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| ng-testGravionLabs/elysionAngular test rules with Vitest and TestBed (components, signals, mocking, async). Use when writing or running tests in Angular. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| nuget-trusted-publishingGravionLabs/elysionSet up NuGet trusted publishing (OIDC) on a GitHub Actions repo — replaces long-lived API keys with short-lived tokens. USE FOR: trusted publishing, NuGet OIDC, keyless NuGet publish, migrate from NuGet API key, NuGet/login, secure NuGet publishing. DO NOT USE FOR: publishing to private feeds or Azure Artifacts (OIDC is nuget.org only). INVOKES: shell (powershell or bash), edit, create, ask_user for guided repo setup. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| plannerGravionLabs/elysionPlan an issue one level down with blockers and sizes, grill the open decisions, create the issues; refine <nr> checks readiness. Use for "plan issue #N" or "refine #N". | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| retroGravionLabs/elysionRetrospective on a run or session: metrics, ranked environment improvements, draft PBIs and lessons. Use for "retro #<issue>" or "analyse this run"; creates no issue without approval. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| setup-biome-huskyGravionLabs/elysionSet up Biome, Husky pre-commit with lint-staged and format-on-save for a plain TS or Node project. Use when asked to add linting, formatting or pre-commit hooks to a non-Angular project. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| setup-prettier-eslint-huskyGravionLabs/elysionSet up ESLint, Prettier, Husky pre-commit with lint-staged and format-on-save for a TS or Angular project. Use when asked to add linting, formatting or pre-commit hooks. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| skills-installGravionLabs/elysion/skills-install: detect the stack and install the matching GravionLabs skill groups into this project or globally (-g) with npx skills. Use for "install the skills", "set up the skills here". | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| ts-create-projectGravionLabs/elysionScaffold a TypeScript/Node.js project (library, CLI, app) with strict tsconfig, Vitest, ESM and CI. Use when asked to create a new TypeScript or Node.js project. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| ts-implementationGravionLabs/elysionTypeScript implementation and test rules (Vitest) extending `implementation`. Use when writing or changing TypeScript or Node.js code. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| ts-mcp-server-generatorGravionLabs/elysionGenerate an MCP server in TypeScript with tools, resources and prompts (@modelcontextprotocol/sdk + zod). Use when asked to create or scaffold an MCP server in TypeScript or Node.js. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| ts-pnpm-workflowGravionLabs/elysionAdopt pnpm as the package manager or migrate from npm (install, lockfile, scripts). Use when starting a Node project or migrating an npm project to pnpm. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| ts-testGravionLabs/elysionTypeScript/Node.js test rules using Vitest (runner config, file naming, mocking, coverage). Use when writing or running tests in a TypeScript or Node.js project. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| create-code-generationtsunami28/MindNovaOrchestrate a feature or fix from story to PR through the team's AI-SDLC workflow, with human checkpoints: story -> plan -> branch -> TDD (>=80% coverage, story-tagged tests) -> update both doc layers -> record decisions as ADRs -> enrich the work item -> review -> PR. Use when the user says "take this story through the process", "run the dev cycle", "do the full workflow on MN-42", or "build this end to end properly". It delegates to focused skills rather than doing each step itself. Do NOT use for a quick one-off edit, a question, or a standalone git or branch request (creating or naming a branch on its own) - use the individual skills directly for those. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| create-refactoringtsunami28/MindNovaImprove the internal structure of existing code without changing its observable behaviour. Use when the user says "refactor this", "clean this up", "simplify this", "extract a method/class", "rename for clarity", "reduce this duplication", or "tidy this without changing behaviour". The defining constraint is behaviour preservation: the tests pass before and after, and the public contract is unchanged. Do NOT use to add or change behaviour, fix a bug, or build a feature (that is create-code-generation), and do NOT use to delete dead code as the primary goal. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| create-run-gatestsunami28/MindNovaRun all the CI code-analysis gates locally against a change, before opening a PR, so failures are caught in seconds instead of after a full pipeline cycle. Use when the user says "run the gates", "check before I push", "will CI pass", "run the CI checks locally", "did I break a gate", or "pre-PR check", or as the verification step at the end of a change. Do NOT use to evaluate a skill's quality (that is governance-validate-skills) or to validate only the artifact graph and docs wiki (that is governance-check-graph); this runs the whole gate set the pipeline runs. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| create-sprint-planningtsunami28/MindNovaAssemble refined, sized stories into an iteration and order them by dependency and value so the build phase starts with a clear, unblocked queue. Use when the user says "plan the sprint", "what should we pick up next", "fill the iteration", "sequence these stories", "order the backlog for the next sprint", or "assign these to the sprint". This is a light coordination step, not a document-producing one. Do NOT use to create or refine a story (that is elaboration-upsert-user-story), to write acceptance criteria (that is elaboration-upsert-user-story-acceptance-criteria), to take a single story through build (that is create-code-generation), or to report the next step on a single work item (that is run-sdlc). | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| create-upsert-documentationtsunami28/MindNovaMaintain BOTH documentation layers as one linked wiki after a change: technical docs in docs/ and functional docs in docs-functional/. Use after implementing or changing a feature, when the user says "update the docs", "sync the documentation", "the docs are out of date", "document how this works", or as the documentation step of a development cycle. Also use when a good answer to a real question deserves to become a page. Reads the layer index first, routes each change to the right layer, cross-links related pages, and flags stale sections. Do NOT use for ADRs (governance-author-adr), the constitution (governance-constitution), or API spec / OpenAPI generation. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| create-verify-test-coveragetsunami28/MindNovaVerify a change is adequately tested before it ships: run the tests, measure line coverage on the changed projects, and confirm every acceptance criterion has a covering test. Use when the user says "is this tested enough", "check the coverage for MN-42", "are all the ACs covered", "verify the tests before the PR", "run the QE checks", or "is this story gate-ready". Do NOT use to WRITE the implementation or the tests (that is create-code-generation), to derive or number the criteria (that is elaboration-upsert-user-story-acceptance-criteria), or to review code style (that is the review step). | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| discovery-map-journeytsunami28/MindNovaMap the customer journey and opportunity landscape for a discovery theme as a diagram, exposing pains and opportunities before any solutioning. Use when the work needs a visual of the experience: phrasings like "map the customer journey", "draw a journey map", "where do users feel pain in this flow", "lay out the opportunity landscape", "visualise the as-is experience", "what are the stages and pain points", or when a Discovery/Spike needs its journey made navigable. Do NOT use to run or synthesise the research itself (that is discovery-synthesize-research), to frame the riskiest assumptions (that is discovery-upsert-hypothesis-canvas), to turn opportunities into stories or create tickets (that is elaboration-upsert-user-story), or to add links to an existing issue (that is governance-enrich-ticket). | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| discovery-synthesize-researchtsunami28/MindNovaTurn raw research into a synthesis anchored on a local Discovery/Spike work item under docs/discovery/. Use when research has been gathered and needs to become navigable findings: phrasings like "synthesise this research", "write up the interview findings", "summarise the research study", "what did the user research conclude", "turn this research into something the team can act on", "anchor this study to a Spike", or when discovery work is done and should feed elaboration. This is the entry point to the discovery phase. Do NOT use to run or collect the research itself (that happens upstream), to create an ordinary feature story (that is elaboration-upsert-user-story), to author an ADR (governance-author-adr), or to add links to an already-synthesised item (governance-enrich-ticket). | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| discovery-upsert-hypothesis-canvastsunami28/MindNovaCapture a product hypothesis (lean canvas) for a discovery theme so discovery stays evidence-driven, not opinion-driven. Use when a discovery direction needs framing before work proceeds: phrasings like "what's our hypothesis here", "frame this as a hypothesis", "write a lean canvas", "what are we assuming", "what's the riskiest assumption", "how would we validate this", "is this a fact or a guess", or when research has surfaced a belief that should be stated and tested. Do NOT use to synthesise raw research (that is discovery-synthesize-research), to write a full PRD or map stories (that is elaboration-upsert-prd-document / elaboration-upsert-user-story), or to author an ADR (governance-author-adr). | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| elaboration-upsert-api-contracttsunami28/MindNovaProduce a machine-readable API specification (OpenAPI 3.x in YAML) for the slice being built, so the build and tests consume a contract instead of prose. Use when designing or changing a REST endpoint, when the user says "design the API for this", "write the OpenAPI spec", "define the contract for MN-42", "what should the request/response shape be", or before code generation begins on a slice that exposes or changes an HTTP surface. This is the L3 keystone: the contract lives in the repo. Do NOT use to author an ADR (that is governance-author-adr), to write feature docs, to generate the implementation (that is create-code-generation), or for non-HTTP work. | Stars: 0 | Updated | Claude CodeCodex | Unverified | 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 | Unverified | 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 | Unverified | 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 | Unverified | 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 | Unverified | 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 | Unverified | 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 | Unverified | 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 | Unverified | 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 | Unverified | Install |