RADAR DES SKILLS · GITHUB

Des Agent Skills utiles, classés selon leur usage réel.

Comparez les Skills vérifiés par fonction, contenu, installations et fiabilité de la source avant de les ajouter.

PÉRIMÈTRE
VÉRIFIÉ
Skills
5 771
dépôts
824
dernière synchronisation
8 sept. 2026
5 771 Skills
kzkski
Communauté

moc-skill

- FIWARE Orion Context Broker (NGSIv2) からエンティティ情報を読み取り専用で取得する。 データ連携基盤・都市OS・スマートシティ基盤・センサーデータ・IoTプラットフォームへの GET クエリ、エンティティ一覧・件数確認、NGSIv2 API 調査が必要なときに能動的に使う。 Orion / NGSIv2 / Context Broker / エンティティ取得 / q クエリ / 地理空間クエリ / Fiware-Service ヘッダー付き基盤アクセスの依頼で発火する。

installations
3
GitHub Stars
0
Mis à jour
11 juin
ohyeh
Communauté

ask-nova

Interview-driven flow picker. Use when the user is unsure which skill/flow/pipeline fits — new project kickoff, cross-domain work, or a fuzzy situation. Reads the three routers live and recommends ONE flow. Not for tasks whose owner is already obvious.

installations
3
GitHub Stars
0
Mis à jour
2 sept.
ohyeh
Communauté

defect-first-review

Perform a read-only, defect-first review of a specified code change and return every actionable finding, reading the whole diff before running anything. Use when another agent delegates review of uncommitted changes, a base-branch diff, a commit, or custom review instructions. Prefer this over the Codex-bundled review-agent, which carries no read-before-you-run gate.

installations
3
GitHub Stars
0
Mis à jour
2 sept.
ohyeh
Communauté

delegation-templates

Fill-in-the-blank prompt templates for delegating work to subagents or tmux workers - SEARCH/LOCATE, IMPLEMENT, REFACTOR, RESEARCH, REVIEW/VERIFY. Invoke BEFORE writing any delegation prompt (Agent tool, agent-tmux worker, or fanout task) so the prompt ships with explicit GOAL, ACCEPTANCE, and REPORT sections instead of a vague ask. Not for deciding WHETHER to delegate or for driving workers after launch (see the tmux-delegate agent and the tmux-agent-tools skill for those).

installations
3
GitHub Stars
0
Mis à jour
2 sept.
ohyeh
Communauté

session-handoff

Creates comprehensive handoff documents for seamless AI agent session transfers. Triggered when: (1) user requests handoff/memory/context save, (2) context window approaches capacity, (3) major task milestone completed, (4) work session ending, (5) user says 'save state', 'create handoff', 'I need to pause', 'context is getting full', (6) resuming work with 'load handoff', 'resume from', 'continue where we left off'. Proactively suggests handoffs after substantial work (multiple file edits, complex debugging, architecture decisions). Solves long-running agent context exhaustion by enabling fresh agents to continue with zero ambiguity.

installations
3
GitHub Stars
0
Mis à jour
2 sept.
ohyeh
Communauté

shared-memory-intake

Curate shared Codex memory when Claude submits findings or Codex reviews, promotes, or maintains task memory.

installations
3
GitHub Stars
0
Mis à jour
2 sept.
ohyeh
Communauté

unknowns-discovery

Find the map/territory gap BEFORE it gets expensive. Invoke when starting a non-trivial task in unfamiliar territory (new module, new technology, work the user has not done before), when acceptance criteria are "I'll know it when I see it", when the user struggles to describe what they want, or when a long-horizon task came back wrong and a blind retry is tempting. Not for typo-level fixes or tasks with fully objective acceptance criteria.

installations
3
GitHub Stars
0
Mis à jour
2 sept.
ohyeh
Communauté

using-design-skills

Meta-router and multi-agent conductor for design work that needs skill selection or a multi-stage pipeline — visual frontend (web pages, landing pages, product UI, mobile screens), data visualization, HTML deliverables (reports/diagrams/plans), artifacts, motion polish, and module/API interface design. The STABLE unified entry point — member skills churn underneath, this router discovers them live, picks one direction authority, delegates image-generation stages to Codex workers, and closes every pipeline with an evidence-first anti-slop quality loop. Do NOT invoke for a one-line CSS/copy tweak, for backend-only work, or when the user explicitly names a single member skill for a single-skill-sized task — those go direct.

installations
3
GitHub Stars
0
Mis à jour
2 sept.
ohyeh
Communauté

using-skills

Top-level map of the skill fleet, for "which skill does this need?" when the answer is not obvious. Invoke when a task's ownership is UNCLEAR or it spans MULTIPLE domains. It routes intent → the right router / skill / recipe and names how to invoke each. When the primary goal already names a domain, enter that domain router or member directly instead. Curates the ADOPTED surface only; the full installed roster lives in the skill manifest.

installations
3
GitHub Stars
0
Mis à jour
2 sept.
ohyeh
Communauté

using-workflows

Meta-router for the workflow recipes in ~/.claude/workflows/ (personal layer) and the current repo's .claude/workflows/ (shadows personal on name collision). Invoke before any loop-shaped work — audits, consensus gates, plan→build lifecycles, findings triage. Even a 1% chance this applies means invoke it.

installations
3
GitHub Stars
0
Mis à jour
2 sept.
ohyeh
Communauté

writing-artifacts

Turn a fuzzy subject — a problem description, an incident, a decision, a long-form idea — into a polished deliverable in the user's chosen format (md, html page, Artifact, image, or plain prose). Runs the writing production line (mine → structure → tighten) with stop-slop discipline, then hands rendering to using-design-skills. Invoke when the user wants something EXPLAINED WELL as a document/page, not when they just want code changed.

installations
3
GitHub Stars
0
Mis à jour
2 sept.
prometheas-labs
Communauté

product-development

Use when the user asks to create a feature, write a PRD or TRD, add user stories, write scenarios, create acceptance criteria, plan implementation, initialize product docs, set up product documentation, create, approve, amend, or validate a Product Constitution, run the Constitution Grill, create or maintain Product Vision, run a Vision Grill, or work anywhere in the product development lifecycle from project setup through implementation planning.

installations
3
GitHub Stars
0
Mis à jour
21 août
getpaseo
Communauté

paseo

Paseo reference for managing projects, workspaces, workspace scripts, agents, schedules, and heartbeats.

installations
3
GitHub Stars
15,8 k
Mis à jour
2 sept.
getpaseo
Communauté

paseo-advisor

Spin up a single agent as an advisor — second opinion on the current task. Use when the user says "advisor", "second opinion", "what does X think", or wants an outside take without delegating the work itself.

installations
3
GitHub Stars
15,8 k
Mis à jour
2 sept.
getpaseo
Communauté

paseo-committee

Form a committee of two high-reasoning agents to step back, do root cause analysis, and produce a plan. Use when stuck, looping, tunnel-visioning, or facing a hard planning problem.

installations
3
GitHub Stars
15,8 k
Mis à jour
2 sept.
getpaseo
Communauté

paseo-handoff

Hand off the current task to another agent with full context. Use when the user says "handoff", "hand off", "hand this to", or wants to pass work to another agent.

installations
3
GitHub Stars
15,8 k
Mis à jour
2 sept.
getpaseo
Communauté

paseo-help

Answer questions about the Paseo product and app, including setup, configuration, connectivity, providers, workspaces, updates, logs, and troubleshooting. Use when a user inside Paseo asks how Paseo works, how to configure it, or why something is broken; use the paseo skill instead to operate agents and workspaces through MCP or the CLI.

installations
3
GitHub Stars
15,8 k
Mis à jour
2 sept.
getpaseo
Communauté

paseo-plugin

Build and manage trusted local Paseo plugins. Use when the user asks to create, edit, install, reload, enable, disable, remove, or troubleshoot a Paseo plugin; add a native surface or sidebar item; use Paseo from plugin code; add plugin RPCs; or contribute composer attachments.

installations
3
GitHub Stars
15,8 k
Mis à jour
2 sept.
getpaseo
Communauté

release-beta

Cut a beta release of Paseo. Use when the user says "release beta", "cut a beta", "ship a beta", "beta release", or "/release-beta".

installations
3
GitHub Stars
15,8 k
Mis à jour
2 sept.
getpaseo
Communauté

release-stable

Cut a stable release of Paseo (fresh patch or minor, or promote from beta). Use when the user says "release stable", "ship stable", "promote", "release:patch", "release:minor", "release:promote", or "/release-stable".

installations
3
GitHub Stars
15,8 k
Mis à jour
2 sept.
vercel-labs
Officiel

next-best-practices

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

installations
3
GitHub Stars
1,6 k
Mis à jour
6 mars
getsentry
Officiel

prompt-optimizer

Creates, optimizes, and iteratively refines agent prompts, system prompts, developer prompts, and reusable prompt templates. Use when asked to improve a prompt, optimize a system prompt, rewrite an agent prompt, tune prompt wording, make a prompt more reliable, port prompts between OpenAI, Claude, or Gemini, or build prompt evals.

installations
3
GitHub Stars
974
Mis à jour
25 août
mengto
Communauté

cinematic-scroll-storytelling

Create cinematic scroll-driven landing pages with Lenis smooth scrolling, GSAP ScrollTrigger, scroll-linked progression, staggered text reveals, sticky card stacks, parallax backgrounds, scroll-scrubbed transitions, footer reveals, and immersive preloaders. Use when analyzing or building premium editorial scroll experiences, sticky project stacks, kinetic typography, or section-by-section storytelling.

installations
3
GitHub Stars
5,7 k
Mis à jour
28 août
elayadesign
Communauté

landing-page-design

Complete system for building high converting landing pages: intake questions, page structure, layout selection, conversion copywriting, SEO, plus strict visual rules for typography, spacing, corner radius, backgrounds, hero layout, icons, and motion. Use this skill whenever building, editing, styling, reviewing, or writing copy for ANY landing page, marketing site, web UI, page section, component, or prototype, even when the user does not mention design, conversion, tokens, or a design system. Always consult it before choosing page sections, headlines, CTAs, fonts, font sizes, spacing values, border radii, background colors, icons, or transitions.

installations
3
GitHub Stars
1,7 k
Mis à jour
29 juil.