Skills.
Give your AI a better way to work.
A skill is a set of written instructions that teaches an AI how to do one job the way it should be done: review a pull request, plan a migration, write the release notes.
Install one here and it travels with your account into Claude, Claude Code, Cursor and every other client you sign in with.
Category: Dev tools
16,902 results · page 382 of 564
- View details
pm-marketSkillDev tools
Use when: you need to understand the market landscape and competitive dynamics, gather industry data, analyze competitors' strengths and weaknesses, or evaluate market opportunities. Do NOT use when: sufficient internal market research data already exists, or only a simple market size estimate is ne
Ready to connect★ 66
- View details
pm-mvpSkillDev tools
Use when: defining the feature scope of a product's first version, filtering an existing requirements list down to MVP features, or determining the minimum viable product boundary. Do NOT use when: the product is already launched and needs a full feature set, or when you only need to organize requir
Ready to connect★ 66
- View details
pm-okrSkillDev tools
Use when: creating OKRs (objectives and key results), breaking down company/product-level goals, goal alignment and cascading, and setting review cadences. Do NOT use when: only a simple to-do list is needed (use pm-iteration); or goals are already fully locked by superiors and need no breakdown.
Ready to connect★ 66
- View details
pm-poolSkillDev tools
Use when: a new requirement needs to be logged and tracked, a requirement's status needs to be changed, the requirement pool needs unified management, or the number of requirements is growing and needs structure. Do NOT use when: there are very few requirements that can be managed directly, or only
Ready to connect★ 66
- View details
pm-portfolioSkillDev tools
Use when: managing multiple product lines requires portfolio decisions, BCG matrix analysis, product lifecycle assessment, or resource allocation. Do NOT use when: a single product needs no portfolio management, or product lines are fixed and need no adjustment.
Ready to connect★ 66
- View details
pm-prioritySkillDev tools
Use when: multiple requirements need to be prioritized, resources are limited and you must decide what to do first, or conflicting requirements need objective scoring. Do NOT use when: there is only one requirement that needs no ranking, or priorities have already been explicitly set by superiors/bu
Ready to connect★ 66
- View details
pm-reportSkillDev tools
Use when: you need to generate data reports, collect and organize user feedback, or perform data-driven analysis and reporting. Do NOT use when: the data is already auto-generated by a BI system and requires no manual analysis.
Ready to connect★ 66
- View details
pm-resourceSkillDev tools
Use when: allocating R&D resources across multiple products, performing ROI evaluation, resolving resource conflicts, or team planning. Do NOT use when: resources are sufficient with no prioritization needed, or a single product requires no multi-project coordination.
Ready to connect★ 66
- View details
pm-resumeSkillDev tools
PM Resume Optimization — analyze, improve, and tailor your PM resume for specific roles Use when: Updating your PM resume, tailoring for a specific role, or getting feedback on your resume
Ready to connect★ 66
- View details
pm-retroSkillDev tools
Use when: after an iteration ends and you need to review lessons learned, improve team processes, or record action items. Do NOT use when: the iteration has not yet ended or the team does not need a formal retrospective.
Ready to connect★ 66
- View details
pm-techSkillDev tools
Use when: liaising with the technical team on technical solutions, assessing technical feasibility, defining technical architecture, or evaluating third-party services. Do NOT use when: the technical solution has already been decided by the technical team, or only a functional description is needed
Ready to connect★ 66
- View details
- View details
provision-environmentSkillDev tools
Provisions a short-lived preview environment.
Ready to connect★ 66
- View details
quick-fixSkillDev tools
Fast bug fix without debug report. One-shot fix for clear, simple bugs. Records fixes in docs/fix/.
Ready to connect★ 66
- View details
release-auditSkillDev tools
Review release evidence for missing approvals and risky changes. Use when validating a release candidate.
Ready to connect★ 66
- View details
rename-preprocessor-scriptsSkillDev tools
Rename a symbol (function, vfunc, vtable, struct member, global variable) across all preprocessor scripts, configs/<GAMEVER>.yaml entries, and tracked source-owned YAML artifacts. Use when a symbol's name changes (class rename, naming-convention fix, etc.), or when splitting a single finder into an
Ready to connect★ 66
- View details
report-builderSkillDev tools
Build weekly status reports from git history and issue tracker exports. Use when preparing a status report.
Ready to connect★ 66
- View details
resolve-pr-conflictSkillDev tools
Resolve an open same-repository GitHub PR conflict by merging its base into the writable dev head, resolving source and config intent semantically, rebuilding conflicted source-owned `bin_artifacts` plus downstream closure, running the repository review/format/test gates, creating one merge commit,
Ready to connect★ 66
- View details
run-validation-until-no-failureSkillDev tools
Use when the user wants to run the IDA validation pipeline (`uv run ida_analyze_bin.py -debug`) repeatedly until it reports zero failures. For each failing skill, diagnose the failure, ask the user how to proceed, and offer several viable solutions. Only when the user explicitly says the failure can
Ready to connect★ 66
- View details
run-vcall-finderSkillDev tools
Run this repository's ad hoc vcall_finder workflow for explicitly selected CS2 modules and one or more symbol names. Use when asked to temporarily find virtual calls for named symbols without registering them in a versioned analysis config.
Ready to connect★ 66
- View details
- View details
setup-api-keySkillDev tools
Guide users through obtaining and configuring a Vapi API key. Use when the user needs to set up Vapi, when API calls fail due to missing keys, or when the user mentions needing access to Vapi's voice AI platform.
Ready to connect★ 66
- View details
sgc-electron-app-relaunchSkillDev tools
Implement and verify full relaunch for Electron desktop apps, distinguishing renderer reloads, user-initiated restarts, dev-mode restarts, and update-install handoffs. Use when the user mentions relaunching the app, menu restart, Cmd+R, app.relaunch, or restarting Electron.
Ready to connect★ 66
- View details
skillsaw-create-pluginSkillDev tools
Create a skillsaw rule plugin — a pip-installable Python package that adds custom lint rules to skillsaw. Walks through scaffolding the package, writing rules against the lint tree, testing, and publishing to PyPI. Use when a user wants to share skillsaw rules across repositories or publish them for
Ready to connect★ 66
- View details
skillsaw-ecosystem-scoutSkillDev tools
Survey the AI coding assistant and agentic tool ecosystem, assess skillsaw's competitive position, identify emerging patterns and missing capabilities, and produce a prioritized strategic report as a GitHub issue. Use when evaluating ecosystem trends and product gaps.
Ready to connect★ 66
- View details
skillsaw-fixSkillDev tools
Fix skillsaw lint violations — apply deterministic autofixes, then resolve the remaining violations with targeted edits guided by `skillsaw explain`. Use when skillsaw reports violations, when asked to clean up lint findings, or after `skillsaw fix` leaves violations behind.
Ready to connect★ 66
- View details
skillsaw-issueSkillDev tools
Use when skillsaw reports a likely false positive, misses an edge case, behaves incorrectly, or needs an RFE. Gather a safe report and, only with explicit user permission, create a feedback bundle or open a GitHub issue.
Ready to connect★ 66
- View details
skillsaw-issue-solverSkillDev tools
Pick up open GitHub issues from collaborators and create PRs to solve them. Use when triaging and resolving reported bugs or feature requests.
Ready to connect★ 66
- View details
skillsaw-issue-triageSkillDev tools
Triage a GitHub issue filed against skillsaw — classify it (bug, feature, docs, question, other), verify its claims against the codebase, enrich it with missing details, and post one structured triage comment. Use when triaging and labeling incoming issues, not to fix them.
Ready to connect★ 66
- View details
skillsaw-onboardSkillDev tools
Onboard a repository to skillsaw — run the linter, triage the findings by rule, apply autofixes, manually fix what remains, set up CI, and create a baseline. Use when adopting skillsaw on a new or existing project.
Ready to connect★ 66
What is a skill?
A skill is plain text, usually a SKILL.md file and the scripts it refers to, written for an AI rather than for a person. It carries the steps, the house rules and the examples a good answer needs, so you stop pasting the same briefing into every new chat.
53,789 of the 54,221 skills listed here can be served through ahel today, and they come from public repositories. Each one has its own page with the instructions themselves on it, so you can read what a skill will tell your AI to do before you install it.
Install one and every AI you use gets it
Installing a skill adds it to your gateway and turns it on in the same step. Claude Code surfaces it as a slash command; any client can read the full instructions with the skill_read tool.
Nothing is copied into a project folder. The instructions are served from your account, so the same skill is there in every AI you connect, and turning it off removes it from all of them at once.