Discover skills
Discover and install skills to enhance your AI agent's capabilities.
| Name | Contains | Score |
|---|---|---|
v0.1.0 Interview the user relentlessly about a plan or design, resolving every branch of the decision tree before producing supporting docs. Specialised for the Tessl monorepo stack. Use when user says "grill me", "interview me about this plan", "help me think through this design", or similar. Contains: grill-me Interview the user relentlessly about a plan or design, resolving every branch of the decision tree before producing supporting docs. Specialised for the Tessl monorepo stack. Use when user says "grill me", "interview me about this plan", "help me think through this design", or similar. | Skills | |
investigate flaky, intermittent, non-reproducible, or ci-only python pytest failures by leading with retrace capture and deterministic replay. use when a user reports flaky pytest tests, random failures, tests that pass locally but fail in ci, async/threading/timing flakes, pytest-xdist issues, fixture leakage, monkeypatch leakage, test isolation failures, dependency/environment-sensitive failures, pytest timeouts, or ai-generated code that breaks tests intermittently. guide the agent to preserve the failed execution as a retrace trace, replay it, inspect runtime state, and use ordinary pytest/source/log checks only as supporting triage. Contains: flaky-pytest-investigator investigate flaky, intermittent, non-reproducible, or ci-only python pytest failures by leading with retrace capture and deterministic replay. use when a user reports flaky pytest tests, random failures, tests that pass locally but fail in ci, async/threading/timing flakes, pytest-xdist issues, fixture leakage, monkeypatch leakage, test isolation failures, dependency/environment-sensitive failures, pytest timeouts, or ai-generated code that breaks tests intermittently. guide the agent to preserve the failed execution as a retrace trace, replay it, inspect runtime state, and use ordinary pytest/source/log checks only as supporting triage. | Skills | |
v0.1.0 Neural search via Exa MCP for web, code, and company research. Use when the user needs web search, code examples, company intel, people lookup, or AI-powered deep research with Exa's neural search engine. Contains: exa-search Neural search via Exa MCP for web, code, and company research. Use when the user needs web search, code examples, company intel, people lookup, or AI-powered deep research with Exa's neural search engine. | Skills | |
Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma). Contains: documentation-lookup Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma). | Skills | |
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates. Contains: github-actions-templates Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates. | Skills | |
C++ coding standards based on the C++ Core Guidelines (isocpp.github.io). Use when writing, reviewing, or refactoring C++ code to enforce modern, safe, and idiomatic practices. Contains: cpp-coding-standards C++ coding standards based on the C++ Core Guidelines (isocpp.github.io). Use when writing, reviewing, or refactoring C++ code to enforce modern, safe, and idiomatic practices. | Skills | |
Create context files (plans, justifications, scratches) in .context/ directory with unique three-word IDs and frontmatter Contains: create-context-file Creates structured context files (plans, justifications, scratches) in the .context/ directory with unique three-word IDs and frontmatter metadata. Use when starting a new task and needing to document a plan or task breakdown, when recording decision rationale or architectural choices as a justification, when saving temporary notes or exploratory thinking as a scratch, or when the user asks to "create a plan", "document my thinking", "save context", "track decisions", or "keep notes" in a structured project context directory. | Skills | |
Review and structure blog articles for the Tessl blog (tessl.io/blog). Use this skill whenever someone asks to review, edit, improve, structure, or give feedback on an article or blog draft. Also use when someone wants to write a new article from scratch, needs help with an article outline, or asks about SEO optimization for Tessl content. Triggers include any mention of blog posts, articles, content review, editorial feedback, SEO for articles, or writing guidance for Tessl or AI Native Dev content. Contains: tessl-article-reviewer Review and structure blog articles for the Tessl blog (tessl.io/blog). Use this skill whenever someone asks to review, edit, improve, structure, or give feedback on an article or blog draft. Also use when someone wants to write a new article from scratch, needs help with an article outline, or asks about SEO optimization for Tessl content. Triggers include any mention of blog posts, articles, content review, editorial feedback, SEO for articles, or writing guidance for Tessl or AI Native Dev content. | Skills | |
Review and structure blog articles for the Tessl blog (tessl.io/blog). Use this skill whenever someone asks to review, edit, improve, structure, or give feedback on an article or blog draft. Also use when someone wants to write a new article from scratch, needs help with an article outline, or asks about SEO optimization for Tessl content. Triggers include any mention of blog posts, articles, content review, editorial feedback, SEO for articles, or writing guidance for Tessl or AI Native Dev content. Contains: tessl-article-reviewer Review and structure blog articles for the Tessl blog (tessl.io/blog). Use this skill whenever someone asks to review, edit, improve, structure, or give feedback on an article or blog draft. Also use when someone wants to write a new article from scratch, needs help with an article outline, or asks about SEO optimization for Tessl content. Triggers include any mention of blog posts, articles, content review, editorial feedback, SEO for articles, or writing guidance for Tessl or AI Native Dev content. | Skills | |
Review and structure blog articles for the Tessl blog (tessl.io/blog). Use this skill whenever someone asks to review, edit, improve, structure, or give feedback on an article or blog draft. Also use when someone wants to write a new article from scratch, needs help with an article outline, or asks about SEO optimization for Tessl content. Triggers include any mention of blog posts, articles, content review, editorial feedback, SEO for articles, or writing guidance for Tessl or AI Native Dev content. Contains: tessl-article-reviewer Review and structure blog articles for the Tessl blog (tessl.io/blog). Use this skill whenever someone asks to review, edit, improve, structure, or give feedback on an article or blog draft. Also use when someone wants to write a new article from scratch, needs help with an article outline, or asks about SEO optimization for Tessl content. Triggers include any mention of blog posts, articles, content review, editorial feedback, SEO for articles, or writing guidance for Tessl or AI Native Dev content. | Skills | |
Spec-driven development on OpenSpec, with mechanical spec-as-source enforcement: a custom 'spec-as-source' OpenSpec schema adds file-ownership (targets) and test-verification ([@test]) metadata to every capability spec, three scripts (link check, ownership check, manifest build) keep code and specs from drifting apart, plus requirement-gathering, spec-writer, work-review, and a session-handoff skill with a proactive context-warning hook. Contains: handoff Gestisce il sistema di passaggio di consegne tra sessioni AI per qualsiasi progetto. Crea, aggiorna e legge file HANDOFF-N.md nella cartella .handoff/ del progetto, mantenendo una knowledge base persistente con documentazione (CLAUDE.md, PROMPTS.md, CLIENTS.md, WORKFLOW.md). Usa questa skill ogni volta che l'utente vuole: - Salvare lo stato ("crea handoff", "salva lo stato", "facciamo il punto", "chiudiamo la sessione", "riprendiamo domani", "passaggio di consegne", "freeze the context", "save state") - Riprendere da una sessione precedente ("riprendi da dove eravamo", "carica handoff", "resume", "continua da HANDOFF", "cosa avevamo fatto") - Inizializzare la knowledge base di un nuovo progetto ("/handoff init") - Aggiornare la documentazione persistente (CLAUDE.md, PROMPTS.md, CLIENTS.md, WORKFLOW.md) Suggerisci proattivamente la creazione di un handoff dopo sessioni lunghe con modifiche importanti, debugging complessi, o decisioni architetturali significative. handoff-skill Traccia bug emersi testando una skill o un plugin, per guidarne l'upgrade. Controparte di handoff orientata al ciclo test → bug → fix di una skill specifica: crea/legge file BUG-N.md in `.handoffskill/<nome-skill>/` con uno STATUS.md aggregato. Usa quando l'utente segnala che una skill non funziona ("questo non funziona", "bug nella skill X"), vuole testarla sistematicamente ("testiamo la skill X"), o riprendere uno stato di test precedente ("riprendi i bug di X"). Invoca anche con "/handoff-skill". openspec-apply-change Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks. openspec-archive-change Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. openspec-explore Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change. openspec-propose Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation. openspec-sync-specs Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change. plan-judge Reviews the entire PLAN.md of a new project through fixed, file-only provider rounds. Triggered by plan-mode when every plan entry is draft; Round 1 alternates Codex and Claude, then returns control to a human checkpoint. plan-mode Builds and maintains openspec/PLAN.md, the human-approved plan that sequences OpenSpec changes toward a stated goal — the tier above tasks.md. Explore read-only, draft entries, then stop and ask for approval; a change cannot start until its entry is approved. Trigger — make a plan, what should we build first, plan the work, roadmap, add this to the plan, approve the plan, why is the plan gate failing, NO-ENTRY, HASH-MISMATCH. prompt-loop Refines an incoming prompt through a bounded score → interview → lock → rewrite loop until it is mechanically good enough (rubric score ≥ 9/10) to feed the SDD workflow. Trigger — automatically before openspec-propose when the request is non-trivial development work; explicitly on: refine this prompt, prompt loop, score my prompt, is this prompt ready. requirement-gathering Structured interview process that turns a vague stakeholder request into clear, actionable requirements before any spec or code is written. Trigger — new feature request, unclear requirements, vague task, clarify scope, before proposing a change. skill-router Single entry point to the spec-as-source workflow: given a request, decides which of the plugin's skills to activate — excluding trivial work first, deriving the current phase from the state of the repo second, and matching descriptions last — then runs the chosen skill inline or in a subagent. Use when you do not know which skill applies, or want the workflow driven for you. Trigger — which skill should I use, what do I do next, route this, start working on X, implement X, propose a change, continue the implementation, I want to build X, help me with this project, non so da dove partire. spec-as-source-setup Installs the spec-as-source OpenSpec schema, enforcement scripts, CI workflow, and pre-commit hooks into a project. Trigger — setup spec enforcement, add spec checks, configure spec-as-source, install spec scripts, add spec CI, install openspec schema. spec-ci-sync Syncs .github/workflows/spec-verification.yml with the test runner and test files declared in specs. Trigger — update CI workflow, sync spec CI, regenerate workflow, CI out of sync with specs, add spec test to CI. spec-loop Runs an autonomous Ralph-style loop over the tasks of an active OpenSpec change: one task per fresh-context agent invocation, mechanically gated by scripts/verify.sh, with runaway guardrails. Trigger — run the loop, ralph loop, autonomous apply, loop the tasks, implement the change unattended. spec-rebuild Deletes all files declared as targets in openspec/specs/**/spec.md and rebuilds them from the specs to verify spec-as-source integrity. Trigger — clean rebuild, verify source of truth, spec drift check, regenerate from specifications, rebuild from spec. spec-verify Runs all spec consistency checks (link integrity, target ownership, manifest build), the test suite, and a semantic drift spot-check, then reports results. Trigger — verify specs, spec check, run spec suite, check spec consistency, validate spec links, spec integrity, spec drift. spec-writer Creates and maintains capability spec.md files under openspec/specs/: requirements, scenarios, targets frontmatter, and Verified by test links. Trigger — write a spec, update a spec, document requirements, create capability spec, spec drift in frontmatter or links. work-review Reviews completed implementation requirement-by-requirement against its capability spec, with file:line evidence, before declaring work done. Trigger — review my work, is this done, verify completeness, check against spec before merging, final review. | SkillsRules | |
administrakt0r/AI-Agents-Safe-Coding-Skills Execute tasks from a track's implementation plan following TDD workflow | Skills | |
administrakt0r/AI-Agents-Safe-Coding-Skills Execute tasks from a track's implementation plan following TDD workflow | Skills | |
administrakt0r/AI-Agents-Safe-Coding-Skills Execute tasks from a track's implementation plan following TDD workflow | Skills | |
ruvnet/RuView Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management | Skills | |
ruvnet/ruvector Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management | Skills | |
ruvnet/agentic-flow Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management | Skills | |
ComposioHQ/awesome-claude-skills Automate Aero Workflow tasks via Rube MCP (Composio). Always search tools first for current schemas. | Skills | |
ComposioHQ/awesome-claude-skills Automate Acculynx tasks via Rube MCP (Composio). Always search tools first for current schemas. | Skills | |
ComposioHQ/awesome-claude-skills Automate Aero Workflow tasks via Rube MCP (Composio). Always search tools first for current schemas. | Skills |
Can't find what you're looking for? Evaluate a missing skill.