Sponsored by

Find leads on Reddit on auto pilot

Topic: skills

17,247 skills in this topic.

paper-planning Guides pre-writing planning for academic papers with 4 structured steps: story design (task-challenge-insight-contribution-advantage), experiment planning (comparisons + ablations), figure design (pipeline + teaser), and 4-week timeline management. Includes counterintuitive planning tactics (write a mock rejection letter to identify weaknesses before writing, narrow before broad claims, design ablations first). Use when: user wants to plan a paper before writing, design story/contributions, plan experiments, create figure sketches, set a writing timeline, or write a pre-emptive rejection letter for planning purposes. Do NOT use for actual writing (use paper-writing), running experiments (use experiment-pipeline), self-reviewing a finished draft (use paper-review), or finding research problems (use research-ideation).
EvoScientist/EvoSkills 141
paper-rebuttal Guides writing effective rebuttals after receiving peer review feedback. Covers review diagnosis (score-driven color-coding), response strategy (champion identification, common-theme consolidation), tactical writing (18 rules), and counterintuitive rebuttal principles. Use when: user received reviewer scores/comments, needs to write a rebuttal or author response, wants to respond to specific criticism (e.g. 'limited novelty', 'missing baselines'), mentions 'rebuttal', 'reviewer comments', 'author response', or 'respond to reviewers'. Do NOT use for pre-submission self-review (use paper-review instead).
EvoScientist/EvoSkills 141
cerul You cannot access video content on your own. Use Cerul to search what was said, shown, or presented in tech talks, podcasts, conference presentations, and earnings calls. Use when a user asks about what someone said, wants video evidence, or needs citations from talks and interviews.
cerul-ai/cerul 120
pr-writing-review Extract and analyze writing improvements from GitHub PR review comments. Use when asked to show review feedback, style changes, or editorial improvements from a GitHub pull request URL. Handles both explicit suggestions and plain text feedback. Produces structured output comparing original phrasing with reviewer suggestions to help refine future writing.
evalstate/fast-agent 3,743
session-investigator Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool call/result correlation, and common failure patterns.
evalstate/fast-agent 3,743
clickhouse Rules when working with ClickHouse database in Gram for analytics and telemetry features
speakeasy-api/gram 227
datadog Use Datadog MCP tools to investigate logs, metrics, traces, and incidents for the Gram project. Activate when the user asks about errors, performance issues, incidents, latency, or wants to search telemetry data.
speakeasy-api/gram 227
frontend Rules and best practices when working on the dashboard and elements React frontend codebases
speakeasy-api/gram 227
golang Rules and best practices when writing and editing Go (Golang) code
speakeasy-api/gram 227
gram-functions A walkthrough of the Gram Functions feature in this codebase
speakeasy-api/gram 227
mise-tasks Rules and best practices for writing and editing mise tasks.
speakeasy-api/gram 227
postgresql Rules when working with PostgreSQL database in Gram
speakeasy-api/gram 227
vercel-react-best-practices React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
speakeasy-api/gram 227
datadog-insights Investigate Gram production health and post a digest to Slack
speakeasy-api/gram 227
codacy-issues-fetcher Retrieve and format Codacy analysis issues by running `scripts/codacy_issues.py` in the ExStruct workspace. Use when users ask to inspect repository or pull-request Codacy findings, filter by severity, or produce structured issue output for review and fix planning.
harumiWeb/exstruct 134
exstruct-cli Use ExStruct CLI to validate, inspect, create, and edit Excel workbooks safely. Trigger when an agent needs `exstruct patch`, `exstruct make`, `exstruct validate`, `exstruct ops list`, or `exstruct ops describe`, especially for create-vs-edit decisions, dry-run workflows, backend constraints, or safe workbook-edit guidance.
harumiWeb/exstruct 134
adr-drafter Draft a new ExStruct ADR or propose an update to an existing ADR from an issue, PR, diff, tests, and specs. Use when an ADR is required or recommended and you need a structured draft with context, decision, consequences, and evidence.
harumiWeb/exstruct 134
adr-indexer Maintain ExStruct ADR index artifacts by scanning ADR files and synchronizing README, index.yaml, and decision-map.md metadata. Use when ADRs are added, updated, superseded, or reclassified and the repository needs a refreshed ADR map for humans and AI agents.
harumiWeb/exstruct 134
adr-linter Review an ExStruct ADR draft for required sections, status values, evidence quality, supersede links, and balanced consequences. Use when an ADR already exists in draft form and you need findings before review or merge.
harumiWeb/exstruct 134
adr-reconciler Audit ExStruct ADRs against current specs, tests, and source code to detect policy drift, missing ADR updates, stale references, and evidence gaps. Use after merges, during periodic ADR audits, or when a review suspects that implementation and ADRs have diverged.
harumiWeb/exstruct 134
adr-reviewer Review an ExStruct ADR draft for decision quality, overlap with existing ADRs and specs, evidence strength, rollout risk, and human-ownership escalations. Use only after adr-linter reports no unresolved high/medium findings on the current draft, and when you need design-review findings before merge or handoff.
harumiWeb/exstruct 134
adr-suggester Determine whether a change in ExStruct needs an ADR, using repository-specific governance and criteria. Use when reading an issue, PR, review thread, or diff and you need a verdict of required, recommended, or not-needed, plus candidate ADR titles and related existing ADRs.
harumiWeb/exstruct 134
cherry-pr-test Test Cherry Studio PRs by checking out the branch, launching the Electron app in debug mode, and running interactive UI tests via CDP.
CherryHQ/cherry-studio 43,310
create-skill Create a new skill in the current repository. Use when the user wants to create/add a new skill, or mentions creating a skill from scratch. This skill follows the workflow defined in .agents/skills/README.md and helps scaffold, validate, and sync new skills.
CherryHQ/cherry-studio 43,310