Discover
Discover and install skills, docs, and rules to enhance your AI agent's capabilities.
| Name | Contains | Score |
|---|---|---|
softaworks/agent-toolkit Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns. | Skills | |
ArabelaTso/Skills-4-SE Analyzes code to identify security-critical time intervals and timing vulnerabilities in authentication, authorization, and time-sensitive security operations. Use this skill when reviewing code for proper timeout enforcement, token expiration, session management, rate limiting, password reset validity, or any time-sensitive security mechanism. Detects missing expiration checks, excessive timeout values, lack of rate limiting, client-side only validation, hardcoded timeouts, and timing attack vulnerabilities. Triggers when users ask to check security timeouts, verify token expiration handling, audit session timeout implementation, review rate limiting, or analyze time-based security controls. | Skills | |
chenhunghan/code-mode-skill Add a "code mode" tool to an existing MCP server so LLMs can write small processing scripts that run against large API responses in a sandboxed runtime — only the script's compact output enters the LLM context window. Use this skill whenever someone wants to add code mode, context reduction, script execution, sandbox execution, or LLM-generated-code processing to an MCP server. Also trigger when users mention reducing token usage, shrinking API responses, running user-provided code safely, or adding a code execution tool to their MCP server — in any language (TypeScript, Python, Go, Rust, etc.). | Skills | |
googolme/run0204 Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices. | Skills | |
Security defaults that belong in every Go HTTP server from day one — CORS, security headers, rate limiting, SQL injection prevention, input validation, secrets management, graceful shutdown, and request timeouts. Contains: go-security-basics Security defaults that belong in every Go HTTP server from day one. CORS, security headers, rate limiting, input validation, SQL injection prevention, CSRF protection, TLS configuration, secrets management, graceful shutdown, and request timeouts. Apply these whenever you create or modify any Go web service -- do not wait for a security review or explicit request. | Skills | |
Production error handling for Express APIs — error middleware, async wrappers, Contains: express-error-handling Production error handling patterns that must be included from day one in any Express API. Apply whenever building, extending, or scaffolding an Express backend -- even if the task only asks for routes or CRUD endpoints. These patterns prevent silent async crashes, inconsistent error formats, stack trace leaks, and dropped connections on deploy. | Skills | |
Build real-time betting and casino game platforms with PubNub Contains: pubnub-live-betting-casino Build real-time betting and casino game platforms with PubNub | Skills | |
whimzyLive/nightshift-ai Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues. | Skills | |
JuliusBrussee/caveman Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode". | Skills | |
Dicklesworthstone/pi_agent_rust Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages. | Skills | |
Hung-Reo/hungreo-openclaw GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured. | Skills | |
benchflow-ai/skillsbench Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modify existing spreadsheets while preserving formulas, (4) Data analysis and visualization in spreadsheets, or (5) Recalculating formulas | Skills | |
ArabelaTso/Skills-4-SE Identify and replace deprecated API usage in source code with modern alternatives. Use when: (1) Modernizing legacy codebases, (2) Upgrading framework versions (React, Django, Spring, etc.), (3) Fixing deprecation warnings in build output, (4) Preparing for major version upgrades, (5) Ensuring code uses current best practices. Supports Python, JavaScript/TypeScript, Java, and other major languages with both AST-based detection and pattern matching for accurate identification and automated replacement with validation. | Skills | |
qsimeon/openclaw-engaging GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured. | Skills | |
attilaczudor/Test GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured. | Skills | |
Test async ordering - event-loop / queue / channel ordering assertions, JS Promise microtask vs macrotask ordering, Python `asyncio.gather` vs `asyncio.wait_for` semantics, Go goroutine + channel happens-before relationships, async/await re-entrancy. Use deterministic schedulers (sinon fake timers, asyncio test mode) to remove run-to-run variance. Use when a callback fires twice, a later response overwrites an earlier one, or a cancelled parent task leaves a child still running - bugs where completion order, not shared memory, is the defect. Contains: async-ordering-tests Test async ordering - event-loop / queue / channel ordering assertions, JS Promise microtask vs macrotask ordering, Python `asyncio.gather` vs `asyncio.wait_for` semantics, Go goroutine + channel happens-before relationships, async/await re-entrancy. Use deterministic schedulers (sinon fake timers, asyncio test mode) to remove run-to-run variance. Use when a callback fires twice, a later response overwrites an earlier one, or a cancelled parent task leaves a child still running - bugs where completion order, not shared memory, is the defect. | Skills | |
v0.16.0 Optimize your skills and plugins: review SKILL.md quality, generate eval scenarios, run evals, compare across models, diagnose gaps, and re-run until scores improve. Contains: compare-skill-model-performance Run task evals across multiple Claude models, compare results side-by-side, and optimise. Use when you want to benchmark a skill across models, compare haiku vs sonnet vs opus performance, run multi-model comparison or benchmark reports, identify model-specific gaps versus universal plugin gaps, evaluate whether a skill works for all model tiers, or validate a skill before publishing it to the registry. optimize-skill-instructions Review and improve your skill with actionable recommendations. Reviews the whole bundle, validates syntax and references, explains rubric, shows before/after scores, and edits the SKILL.md and its reference docs. Use when reviewing skill quality, improving a SKILL.md or its reference files, checking scoring dimensions and quick wins, auditing progressive disclosure and orphaned bundle files, generating improvement recommendations, running a post-edit quality audit, creating approval-gated change proposals, or automating the skill review workflow. For the full optimization cycle (review + evals + improve), use `optimize-skill-performance-and-instructions`. optimize-skill-performance-and-instructions Run the full optimization cycle for a plugin — review best practices, generate eval scenarios, run BOTH activation evals (does the skill self-activate?) and content evals (does the plugin help solve tasks?), diagnose gaps, fix, and re-run until scores improve. Use when someone says "optimize my skill", "improve my plugin", "run evals", "benchmark my plugin", or wants to measure and improve how well a plugin helps agents solve tasks. optimize-skill-performance Run task evals, analyze results, diagnose failures, apply targeted fixes, and re-run to verify improvements. Use when debugging evaluation scores, fixing failing or regressed criteria, analyzing why eval criteria pass or fail, reviewing eval rubric quality and redundant criteria, tracking before/after score improvements, editing plugin content to fix specific failing behaviors, or improving agent performance based on eval evidence. setup-skill-performance Generate eval scenarios from a Tessl plugin (a packaged skill bundle), run baseline + with-context evals, and present results. Use when setting up an evaluation pipeline, running benchmarks, generating test scenarios, measuring skill performance or accuracy, scoring how well a skill helps agents solve tasks, or evaluating skill effectiveness before publishing. | Skills | |
rikdc/ai-skills Creates and maintains CHANGELOG.md in Keep a Changelog format, including adding entries and cutting releases. Use when the user asks to update the changelog, add a changelog entry, or record a release. | Skills | |
Skills are the new Code by Guy Podjarny Contains: talk-podjarny-skills-are-the-new-code-aindc Use when the user asks about Guy Podjarny's talk "Skills are the new Code" (AI Native Dev Con Spring 2026 keynote) — the agentic software stack (tools, context, harnesses, factory lines), Context Development Life Cycle (CDLC), skill rot, negligent vs malicious skills, evals for skills, skill dependency management, or his five-tool framework (static analysis, evals, dependency management, security, observability). ALSO use proactively (even if the talk is not mentioned) when the user is writing a skill spec / template / style guide, designing a shared skill library or skill registry, defining skill quality / safety / metadata standards, versioning skills, writing skill rot or lifecycle policy, addressing agent supply chain security, or defining evals for skills — to embed one relevant verbatim quote from Guy's keynote into the deliverable. | Skills | |
v0.2.10 Create and migrate repo-defined Tessl schedules in a project's tessl.json. Turns a plain-language task and cadence into a validated schedules entry, optionally authors its repo-local skill, and moves an existing UI/CLI schedule into version control. Contains: schedule-migrate Migrate an existing UI- or CLI-created Tessl schedule into a repo-defined entry in tessl.json. Use when the user wants to move a schedule into version control ("put my schedule in the repo", "migrate this schedule to tessl.json", "make my scheduled run repo-defined"), or convert an app-defined schedule to a repo-defined one. The skill lists live schedules, reads the chosen one's config, writes the equivalent tessl.json entry, validates it, and optionally deletes the old schedule once the new one is confirmed. Not for creating a schedule from scratch (use schedule-setup). schedule-setup Create a repo-defined schedule in a project's tessl.json from a plain-language description, optionally authoring the repo-local skill it runs. Use when the user wants to schedule a skill to run on a recurring cadence ("run X every morning", "kick off the report nightly", "schedule this weekly"), set up a recurring launch run, or add a `schedules` block to tessl.json. The user describes the task, cadence, and environment in plain words; this skill chooses the most readable supported schedule format, adds and validates the entry, and explains what happens on push. Not for one-off runs (use `tessl launch`) or for moving an existing UI/CLI schedule into the file (use schedule-migrate). | Skills |
Can't find what you're looking for? Evaluate a missing skill.