Discover and install skills to enhance your AI agent's capabilities.
| Name | Contains | Score |
|---|---|---|
brianlovin/agent-config Use Bun instead of Node.js, npm, pnpm, or vite. Provides command mappings, Bun-specific APIs, and development patterns. | Skills | |
softaworks/agent-toolkit Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams, document system architecture, visualize software structure, create C4 diagrams, or generate context/container/component/deployment diagrams. Triggers include "architecture diagram", "C4 diagram", "system context", "container diagram", "component diagram", "deployment diagram", "document architecture", "visualize architecture". | Skills | |
softaworks/agent-toolkit Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams, document system architecture, visualize software structure, create C4 diagrams, or generate context/container/component/deployment diagrams. Triggers include "architecture diagram", "C4 diagram", "system context", "container diagram", "component diagram", "deployment diagram", "document architecture", "visualize architecture". | Skills | |
softaworks/agent-toolkit React useEffect best practices from official docs. Use when writing/reviewing useEffect, useState for derived values, data fetching, or state synchronization. Teaches when NOT to use Effect and better alternatives. | Skills | |
fernandezbaptiste/rails_ai_agents Implements transactional emails with Action Mailer and TDD. Use when creating email templates, notification emails, password resets, email previews, or when user mentions mailer, email, notifications, or transactional emails. | Skills | |
samber/cc-skills-golang Security best practices and vulnerability prevention for Golang — injection (SQL, command, XSS), cryptography, path traversal, SSRF and HTTP security headers, cookies, secrets management, memory safety, PII in logs, STRIDE/DREAD threat modeling, plus `gosec` SAST, race detection, and fuzz testing. Apply when writing, reviewing, or auditing Go code for security, or when touching crypto, file or network I/O, secrets, user input, or authentication. Not for non-exploitable defensive bugs such as nil panics or slice aliasing (→ See `samber/cc-skills-golang@golang-safety` skill), dependency vulnerability scanning with govulncheck (→ See `samber/cc-skills-golang@golang-dependency-management` skill), or wiring security scanners into CI pipelines (→ See `samber/cc-skills-golang@golang-continuous-integration` skill). | Skills | |
SpecterOps/Nemesis Manages Python package dependencies. Use when adding, upgrading, removing, or syncing Python/pypi packages in projects or libs. | Skills | |
qsimeon/openclaw-engaging Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn/run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Claude Code: use --print --permission-mode bypassPermissions (no PTY). Codex/Pi/OpenCode: pty:true required. | Skills | |
v2.17.1 AI Unified Process core - stack-agnostic requirements, entity model, and use cases Contains: entity-model Creates entity model documents with Mermaid.js ER diagrams and attribute tables defining entities, relationships, data types, and validation rules. Use when the user asks to "create an entity model", "design a data model", "draw an ERD", "define database schema", "model entities", or mentions entity-relationship diagram, ER diagram, database design, or data modeling. Also trigger whenever the task is to produce, write, or design an entity model or data model document (e.g. docs/entity_model.md) from a requirements catalog — including phrasings like "data model design", "the team needs an entity model before development", or a request to document entities with attributes, data types, precision, and validation or cross-attribute constraints. requirements Gathers, organizes, and documents software requirements into structured catalogs with functional requirements (user stories), non-functional requirements (measurable quality attributes), and constraints. Use when the user asks to "write requirements", "create a PRD", "gather requirements", "document feature specs", "write user stories", "define NFRs", "list constraints", "write a glossary", "define domain terms", or mentions requirements catalog, requirements analysis, product requirements document, feature specification, or glossary. reverse-engineer Reverse-engineers an existing software project into AI Unified Process artifacts: a PlantUML use case diagram, per-use-case specification documents, and an entity model with a Mermaid ER diagram. Use when the user asks to "reverse engineer this codebase", "extract use cases from existing code", "document the system we already have", "generate use case specs from controllers", "derive an entity model from the database", "create AI Unified Process artifacts from a legacy project", or mentions reverse engineering, legacy documentation, or onboarding an inherited codebase. Trigger this skill whenever a user wants to produce use cases, an ER diagram, or a use case diagram from code that already exists rather than from a fresh vision document — even if they don't say "reverse engineer" explicitly. spec-review Reviews the specification artifacts in docs/ (requirements, use case diagram, use case specifications, test cases, BPMN process models, entity model, glossary) against each other in two parts: a deterministic lint that can block a build (missing specifications, duplicate or unresolved ids, uncovered FRs, unmapped BPMN activities, weak words, glossary synonyms) and an advisory semantic review (contradicting or duplicated rules, wrong level of detail, missing alternative flows, untestable rules, ambiguity, actors, NFRs and constraints, entity model consistency), plus a traceability matrix on request. Use when the user asks to "review the specs", "lint the use cases", "find contradictions", "is this use case ready", "show the traceability matrix", "which use cases realize FR-014", or wants a specification quality gate in CI. It reports only and never edits a specification; checking code against a specification is /coverage-check. test-case Creates end-to-end test case documents (TC-*.md) that chain several use cases into one user journey with a step-by-step Flow table, concrete test data, and final validations. Use when the user asks to "create a test case", "write a test case", "define an end-to-end scenario", "document a user journey for testing", "chain use cases into a test", or mentions a test case document, TC-001, journey test, or end-to-end test scenario. Also trigger whenever the user lists several use case IDs (UC-*) and wants one test definition spanning them, or wants test cases derived from a business process, a BPMN process model, or a .bpmn file (one test case per path through the process) — the resulting TC-* document is what e2e test skills (e.g. /playwright-test TC-001) automate. use-case-diagram Creates or updates PlantUML use case diagrams defining actors, use cases, and their relationships from requirements. Use when the user asks to "create a use case diagram", "draw a UML diagram", "map actors to use cases", "generate a .puml file", or mentions PlantUML, use case overview, actor diagram, or system use cases. use-case-spec Creates detailed use case specification documents with actors, preconditions, main success scenarios, alternative flows, postconditions, and business rules. Use when the user asks to "write a use case", "specify a use case", "document system behavior", "define scenarios", "write a functional spec", or mentions use case specification, acceptance criteria, or user scenarios. Also trigger whenever the task is to write use case specification documents for the use cases in a use case diagram (e.g. docs/use_cases.puml) — including phrasings like "detailed use case specifications before writing any code", "one file per use case", or a request to cover the happy path, alternative flows, postconditions, and business rules for each use case. | Skills | |
v1.0.2 Interactive skill creation and eval-driven optimization. Triggers: create a skill, make a skill, new skill, scaffold skill, optimize skill, run evals, improve skill. Uses AskUserQuestion for interview; WebSearch for research; Bash for eval execution. Outputs: complete skill directory with SKILL.md, tile.json, evals, and repo integration. Contains: skill-maker Use this skill any time someone wants to create, scaffold, build, fix, improve, benchmark, or optimize a Tessl/Claude skill — even if they don't say 'tessl' explicitly. If the request involves making a new skill ('create a skill for X', 'build me a skill that does Y', 'scaffold a skill called Z'), fixing or completing an existing one (missing tile.json, broken repo integration, low eval scores, description not triggering), or running and iterating on evals, invoke this skill. The full workflow covers: structured interview → SKILL.md + tile.json + rules/ scaffolding → README/CI repo integration → tessl tile lint → optional Tessl CLI pipeline (skill review, scenario generate/download, eval run) → hand-authored evals or LLM-as-judge fallback → benchmark logging. Do NOT use for: editing application code, debugging, refactoring, writing general documentation, or creating presentations. | Skills | |
Content creator for tessl.io — generates publish-ready blog articles with SEO metadata, Tessl house style, and technical authority. Contains: article-creator Drafts, edits, or produces publish-ready blog articles for tessl.io including thought leadership, skill showcases, tutorials, news/analysis, or comparisons. Use whenever the user asks for a tessl.io article, blog post draft, content for the Tessl blog, or wants to write/review content following Tessl's editorial standards, SEO metadata, and house style rules. | Skills | |
Intelligent-Internet/ii-agent Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. | Skills | |
Intelligent-Internet/ii-agent Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. | Skills | |
XiaomiMiMo/MiMo-Code Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script. | Skills | |
g14wx/staffSync Reviews and refactors .NET/C# code: fixes async patterns, validates DI registration, corrects error handling, adds documentation, enforces style conventions. USE FOR: review C# code, audit project, enforce coding standards, apply .NET best practices, clean up code, fix style issues, apply coding standards, tidy up this file, make this idiomatic C#, fix code quality issues, get PR-ready, prepare for code review, add documentation, fix async patterns, check DI registration, check error handling, fix configuration, bring this up to standard, make this code production-ready. DO NOT USE FOR: non-.NET codebases, read-only .NET questions, trivial single-variable edits. | Skills | |
LedgerHQ/agent-skills Map developer intent and natural language to the correct Ledger Device Management Kit (DMK) components, operations, and API methods. Use when a developer's request is phrased informally, incompletely, or in terms of outcomes rather than API methods, when the intent is ambiguous and needs mapping to a specific DMK component or operation, or when a developer asks 'how do I...', 'what's the difference between...', or describes a symptom rather than an API. | Skills | |
thoughtboat/copilot-skills-that-work Reviews and refactors .NET/C# code: fixes async patterns, validates DI registration, corrects error handling, adds documentation, enforces style conventions. USE FOR: review C# code, audit project, enforce coding standards, apply .NET best practices, clean up code, fix style issues, apply coding standards, tidy up this file, make this idiomatic C#, fix code quality issues, get PR-ready, prepare for code review, add documentation, fix async patterns, check DI registration, check error handling, fix configuration, bring this up to standard, make this code production-ready. DO NOT USE FOR: non-.NET codebases, read-only .NET questions, trivial single-variable edits. | Skills | |
anthropics/cwc-workshops How to rank and pick a supplier for a SKU. Load this whenever a task involves choosing a supplier, comparing quotes, or creating a purchase order. | Skills | |
angular/angular Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, naming conventions, or CLI tooling. | Skills | |
ReScienceLab/opc-skills SEO & GEO (Generative Engine Optimization) for websites. Analyze keywords, generate schema markup, optimize for AI search engines (ChatGPT, Perplexity, Gemini, Copilot, Claude) and traditional search (Google, Bing). Use when user wants to improve search visibility, search optimization, search ranking, AI visibility, ChatGPT ranking, Google AI Overview, indexing, JSON-LD, meta tags, or keyword research. | Skills |
Can't find what you're looking for? Evaluate a missing skill.