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 429 of 564
- View details
skodanakannanirSkillDev tools
RÚV + Vísir + Heimildin opinion-poll aggregators — all-pollster party support (Alþingi + Reykjavík) and ESB; try maskina first.
Ready to connect★ 54
- View details
smith-bankSkillDev tools
Captures ideas mid-conversation and stores them in the vault for later processing. Use when the user wants to save an idea, park a thought, or come back to something later. Supports listing, processing, editing, and prioritizing banked ideas.
Ready to connect★ 54
- View details
smith-bugfixSkillDev tools
Lightweight fix workflow for bugs and small changes. Autonomous from invocation through merged PR — no questions gate, no spec generation, no planning phase.
Ready to connect★ 54
- View details
smith-checklistSkillDev tools
Generate a custom checklist for the current feature based on user requirements.
Ready to connect★ 54
- View details
smith-clarifySkillDev tools
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
Ready to connect★ 54
- View details
smith-constitutionSkillDev tools
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
Ready to connect★ 54
- View details
smith-debugSkillDev tools
Diagnostic workflow that systematically gathers evidence, identifies root causes, and produces a structured debug report. Read-only — does not modify code. Output feeds into /smith-bugfix if a fix is needed.
Ready to connect★ 54
- View details
smith-exploreSkillDev tools
Pre-change exploration — audits codebase for system-wide impacts, identifies touch points, and surfaces conflicts before proceeding with smith-new or other workflows.
Ready to connect★ 54
- View details
smith-finishSkillDev tools
End-of-session workflow that commits, pushes, merges to main, updates specs, and cleans up the workspace.
Ready to connect★ 54
- View details
smith-helpSkillDev tools
Central reference for all Smith commands — overview, detailed help per command, syntax, flags, and workflow context.
Ready to connect★ 54
- View details
smith-migrate-specsSkillDev tools
One-time migration of existing flat spec folders into the system-based hierarchy under .specify/systems/.
Ready to connect★ 54
- View details
smith-newSkillDev tools
Start a new feature from scratch or from conversation context. Conversational requirements gathering, planning, questions gate, then fully autonomous build.
Ready to connect★ 54
- View details
smith-reflectSkillDev tools
Analyzes a completed Smith workflow (build, bugfix, audit) and extracts lessons about what worked and what didn't. Updates the Ledger with new patterns and antipatterns. Use after a workflow completes or fails, or manually to review recent work.
Ready to connect★ 54
- View details
smith-specifySkillDev tools
Create or update the feature specification from a natural language feature description.
Ready to connect★ 54
- View details
social-asset-batchSkillDev tools
Generate organic social asset batches (feed, story, reel, carousel, short) sized per platform and toned per channel.
Ready to connect★ 54
- View details
star-office-helperSkillDev tools
Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation. Use when users ask for Star Office setup, URL/port connection, Unauthorized page diagnosis, Python venv/pip issues (PEP 668), preview panel wiring, real-ti
Ready to connect★ 54
- View details
star-your-harnessSkillDev tools
Helps users build their own AI harness working directory from scratch. Starts with a brief four-question interview (what you do, what you want AI to help with, where your materials are scattered, where to put things), then generates a directory skeleton based on your profession, including an entry C
Ready to connect★ 52
- View details
startup-founder-problem-framingSkillDev tools
Frame a startup idea through customer empathy, JTBD, urgency, current alternatives, and the shortest path to user value.
Ready to connect★ 54
- View details
startup-ideal-customer-profileSkillDev tools
Define the startup's beachhead customer with context, JTBD, buying behavior, pain points, and disqualification rules.
Ready to connect★ 54
- View details
startup-strategic-diagnosisSkillDev tools
Diagnose a startup idea through market timing, alternatives, SWOT, strategic pressure points, and must-be-true assumptions.
Ready to connect★ 54
- View details
startup-value-propositionSkillDev tools
Build a startup value proposition through customer, problem, before-state, solution, after-state, and alternatives.
Ready to connect★ 54
- View details
state accountsSkillDev tools
Icelandic state accounts actuals (Fjársýsla) — yearly revenue/expense 2015+; pre-2015 balance via Hagstofan THJ05211; 36 policy areas (málefnasvið).
Ready to connect★ 54
- View details
status-colors-and-errorsSkillDev tools
Keep status and error colours minimal and consistent — too many semantic colours confuse users. Each colour must mean exactly one thing. Errors should be recoverable, large failures must be prevented, and the UI should always give the user a path forward. Use when designing status indicators, error
Ready to connect★ 54
- View details
sticky-and-fixed-elementsSkillDev tools
Sticky and fixed positioning keeps critical UI persistent as the user scrolls — headers at the top, toolbars at the bottom on mobile. Use deliberately: too many fixed layers create visual noise and reduce content area. Use when designing navigation headers, bottom toolbars, floating action buttons,
Ready to connect★ 54
- View details
tab-navigationSkillDev tools
Tabs organise related content under a shared context — switching tabs swaps the view without leaving the page. Use when a screen has multiple distinct content areas that share a common header or action set, and when the user needs to switch between them frequently. Use when designing tabbed layouts,
Ready to connect★ 54
- View details
translate-slovakSkillDev tools
Glossary and phrasing rules for Slovak (sk) translations of Editoria11y and Sa11y strings. Read before writing or reviewing src/lang/sk.js or src/sa11y-lang/sk.js.
Ready to connect★ 54
- View details
ui-context-and-scopeSkillDev tools
UI should make it immediately clear where the user is, what context they are operating in, and what their actions will affect. Use lines, regions, colour areas, breadcrumbs, and scope labels to communicate hierarchy and context — especially in deep navigation structures or multi-section layouts.
Ready to connect★ 54
- View details
ui-densitySkillDev tools
UI density — how much information and how many features appear at once — should match the primary platform and user type. Desktop supports dense, feature-rich interfaces; mobile requires focused, reduced layouts. Enterprise power users tolerate higher density than occasional users. Use when designin
Ready to connect★ 54
- View details
umferdSkillDev tools
Icelandic traffic counters (Vegagerðin) — real-time 15-min counts, 7-day rolling daily totals, 168+ stations via WFS.
Ready to connect★ 54
- View details
ust-gisSkillDev tools
Environment Agency of Iceland GIS — open WFS layers for contaminated land, water, protected areas, noise and wastewater.
Ready to connect★ 54
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,788 of the 54,220 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.