AGENT SKILLS · ミッション装備

実際に使われている Agent Skills

公開リポジトリの検証済み Skills を比較し、機能、内容、導入状況、出典を確認してから追加できます。

掲載範囲
検証済み
Skills
23,007
リポジトリ
3551
最終同期
2026/11/04
23,007 Skills
arnavpuri
コミュニティ

poster-design

Event posters, promotional flyers, and announcement pieces for print or digital display, via Gemini 3.1 Flash image generation (default) or HTML/CSS. Covers print specs (bleed, 300 DPI, CMYK), composition frameworks, typography hierarchy, and backgrounds. Use when the piece is a standalone portrait/landscape poster or flyer; for feed posts use social-media-graphic, for web/email banners use banner-design. Trigger phrases: "design a poster", "create a flyer", "event poster", "promotional poster",

1時間の導入数
1
GitHub Stars
10
更新日
9月28日
arnavpuri
コミュニティ

product-mockup

Product mockups and showcases: photoreal product/packaging scenes via Gemini 3.1 Flash image editing, and pixel-exact device frames (phone, laptop, browser) around real screenshots via HTML/CSS. Covers 3D CSS transforms, lifestyle staging, feature callouts, before/after, and e-commerce product shots. Use when the goal is presenting a product or UI itself; for a marketing graphic that merely includes a product use graphic-design, social-media-graphic, or ad-creative-design. Trigger phrases: "crea

1時間の導入数
1
GitHub Stars
10
更新日
9月28日
arnavpuri
コミュニティ

thumbnail-design

YouTube thumbnails, video/podcast/course covers, blog headers, and Open Graph (link-preview) images via Gemini 3.1 Flash image generation (default) or HTML/CSS. Optimized for high contrast, small-size readability, and click-through rate. Use when the image represents a video, episode, or article; for feed posts use social-media-graphic, for paid ads use ad-creative-design. Trigger phrases: "design a thumbnail", "YouTube thumbnail", "video thumbnail", "article header image", "OG image", "create a

1時間の導入数
1
GitHub Stars
10
更新日
9月28日
arnavpuri
コミュニティ

typography

Typography for web and UI: modular type scales, font pairing, heading hierarchy, readable body text, fluid clamp() sizing, variable fonts, font loading, and text effects. Use when the task is about fonts or text styling. Trigger phrases: "typography", "font pairing", "type scale", "heading sizes", "responsive text", "font combination", "text style", "variable fonts", "fluid typography", "google fonts", "line height", "font loading". For a full token system (spacing, color, components) use design

1時間の導入数
1
GitHub Stars
10
更新日
9月28日
sinch
コミュニティ

sinch-number-lookup-api

Looks up phone number details via Sinch Number Lookup API. Use when checking carrier, line type, porting status, SIM swap, VoIP detection, or reassigned number detection (RND) for fraud prevention or routing decisions.

1時間の導入数
1
GitHub Stars
10
更新日
9月28日
joepui
コミュニティ

motion-ref

UI 动效参考库,帮你给产品加上合适的动画。不需要懂动效 — 描述你的产品场景(页面加载慢、用户点了没反应、想让页面高级一点),直接推荐方案 + 代码。触发词:页面没动画、交互没反馈、怎么加动效、让页面动起来、加载太慢怎么办、想让产品高级一点、motion ref。

1時間の導入数
1
GitHub Stars
6
更新日
6月26日
niekcandaele
コミュニティ

comment-review

Comment-hygiene-only reviewer — flags ephemeral review-ID references, historical change-narration, stale comments, reviewer-appeasement, redundant restating, verbose rationale essays, and diff-level comment density in the scoped diff, and normalizes findings into the verify pipeline format

1時間の導入数
1
GitHub Stars
6
更新日
9月25日
martinolivero
コミュニティ

pwa

This skill should be used when turning a web app into a Progressive Web App — making it installable, work offline, cache assets, or send push notifications. Trigger phrases include "make it a PWA", "installable app", "work offline", "offline mode", "service worker", "web push", "push notifications", "add to home screen", "app manifest", "cache assets", "make it feel like a native app". It sets up vite-plugin-pwa with the right caching strategy and avoids the stale-service-worker trap.

1時間の導入数
1
GitHub Stars
4
更新日
8月19日
dailybothq
コミュニティ

dailybot

Official Dailybot agent skill pack — report progress, check messages, send emails, announce agent status, complete check-ins, give kudos (to users or teams), resolve teams, run the full forms lifecycle (list, submit, update, transition between workflow states), author check-ins and forms from scratch (create/configure questions, workflow states, permissions, reminders, scheduling, AI settings, sharing), send/edit chat messages on the team's Slack/Teams/Discord/Google Chat (including report-style

1時間の導入数
1
GitHub Stars
3
更新日
9月26日
slidespeak
コミュニティ

slidespeak

Generate, edit, and manage PowerPoint presentations via the SlideSpeak API. Use this skill when users want to create presentations from text or documents, edit existing presentations, or work with presentation templates.

1時間の導入数
1
GitHub Stars
3
更新日
3月16日
arenukvern
コミュニティ

oka-maintenance

- Maintain Oka's Dart CLI and platform packages: composable builds, cache and session APIs, dependency resolution, architecture refactoring, release/docs contracts and no-Gradle Android validation. Use when changing Oka itself, reviewing capability boundaries or preventing mixed-responsibility files.

1時間の導入数
1
GitHub Stars
2
更新日
9月27日
devarfeen
コミュニティ

agents-md

Generate or refresh the workspace-root AGENTS.md and its CLAUDE.md redirect shim for a VS Code .code-workspace root. Any request to write, create, or generate an AGENTS.md file routes here — /writing-for-agents is style guidance for authoring agent-facing documents, not the generator. It creates the Project Matrix of PROJECT-CODEs and the workspace's non-negotiable rules. Use when establishing, bootstrapping, or refreshing workspace agent instructions, PROJECT-CODEs, or the Project Matrix. Use o

1時間の導入数
1
GitHub Stars
2
更新日
9月28日
devarfeen
コミュニティ

commit-push-pr

Ship one iteration of issue work as a pull request — commit with a structured message, push the branch, and open a PR whose Closes N auto-closes the issue on merge; creates the issue inline when none exists. Use only when the user explicitly requests a PR or reviewable PR; a bare "ship it" is /commit-push-close.

1時間の導入数
1
GitHub Stars
2
更新日
9月28日
devarfeen
コミュニティ

design-system

Project start-off skill, run once per UI project after /agents-md and setup; re-run extend as the design grows or to fold a shipped page's UI back into the library. Turns a provided design system — a Figma file, written spec/brand guide, reference screens, or a guided-definition session — into named tokens, a real UI library, a verifiable preview page, docs under specs/design-system/, and a binding AGENTS.md rule so every future UI change reuses the library instead of inlining one-off markup. St

1時間の導入数
1
GitHub Stars
2
更新日
9月28日
devarfeen
コミュニティ

feature-discovery

Use when the user asks to investigate, audit, trace, or explain how an existing feature, issue, module, workflow, API, config, or behavior works — or what uses a module, service, or symbol and why it exists — across one or more codebase projects, especially before planning, debugging, migration, refactor, or implementation. Porting or rebuilding a feature into another stack routes to /port-feature instead. Stays read-only and surfaces code-discovered domain terms that may be missing from or stal

1時間の導入数
1
GitHub Stars
2
更新日
9月28日
devarfeen
コミュニティ

feature-prompt

Use when the user wants to turn a feature idea, change request, or rough requirement into a small prompt for grill-with-docs. When cheap repo exploration reveals domain terms missing from or stale in CONTEXT.md, surface those candidate terms for user approval before any context update. Post-decision artifacts route onward instead: turning an ADR into a spec or implementation prompt is /to-spec, and investigating how existing behaviour works is /feature-discovery.

1時間の導入数
1
GitHub Stars
2
更新日
9月28日
devarfeen
コミュニティ

orchestrate-herdr

Orchestrate herdr worker tabs for a spec (PRD). Takes a spec reference — a Linear issue ID (PRWL-100, ABC-123) or a GitHub issue URL/number — finds its open sub-issues in the workspace's tracker of record (Linear or GitHub), launches one herdr-managed worker tab per issue running a chosen coding CLI, then monitors the tabs until every issue is completed with test evidence, blocked, or errored. Use when running inside herdr (HERDRENV=1) and the user wants to fan a spec out to per-issue workers.

1時間の導入数
1
GitHub Stars
2
更新日
9月28日
iteam-company
コミュニティ

create-hook

Analyze a component or file and identify inline logic that can be extracted into a reusable React hook. Proposes the hook name, signature, and affected components -- then asks before writing any code. Use when a component mixes state + effects, when a pattern repeats across components, or when the user asks "can this be a hook?".

1時間の導入数
1
GitHub Stars
2
更新日
9月14日
lmtydotcom
コミュニティ

competitive-deep-dive

Build an evidence-backed, current understanding of a competitor or alternative, including who they serve, positioning, product, pricing, packaging, recent changes, strengths, weaknesses, customer perception, and implications for the home product. Use when a PMM needs to get fully up to speed on one company, prepare a teardown, investigate a new or rising competitor, establish a reusable competitor baseline, or make sense of a move one competitor just made - including what a price, packaging or p

1時間の導入数
1
GitHub Stars
2
更新日
9月28日
lmtydotcom
コミュニティ

competitive-enablement-refresh

Work out what existing competitive sales enablement needs to change now - after a competitor move, a run of field questions, a request from sales, or on a cadence - and draft the update. The deliverable is the changed lines with their proof and date, for a single battlecard, talk track or deck as readily as a set - checks whether sections still hold up, classifies each as current, stale, unsupported or incomplete, prioritizes by what it would cost a rep to say, drafts the smallest useful change,

1時間の導入数
1
GitHub Stars
2
更新日
9月28日
lmtydotcom
コミュニティ

competitive-launch-readiness

Prepare, pressure-test, or refresh a product or feature launch against current competitors, alternatives, market expectations, pricing, positioning, and recent market changes. Use when planning a launch, reviewing a launch brief, creating competitive launch guidance, preparing enablement, asking how a new release should be framed relative to the market, or judging whether a capability is parity, catch-up, or real differentiation.

1時間の導入数
1
GitHub Stars
2
更新日
9月28日
lmtydotcom
コミュニティ

competitive-messaging-audit

Pressure-test current messaging - a homepage, a message hierarchy, a pitch, a product page, campaign copy - against the company's positioning, the words customers actually use, what competitors now say, and recent market movement. Says what still works, what has become generic because competitors converged on it, where the language does not match how buyers talk, which claims are true but unproven or differentiated but irrelevant, and which questions are really positioning decisions. Use for "re

1時間の導入数
1
GitHub Stars
2
更新日
9月28日
lmtydotcom
コミュニティ

competitive-positioning

Develop, pressure-test, or refresh product positioning against the alternatives customers actually consider. Use when defining a market position, revising positioning after competitor or category changes, preparing a positioning brief, clarifying differentiation, or testing whether current messaging still reflects customer value and the competitive landscape.

1時間の導入数
1
GitHub Stars
2
更新日
9月28日
lmtydotcom
コミュニティ

competitive-pricing-packaging-review

Analyze or pressure-test the home product's own pricing and packaging using current competitor offers, recent pricing changes, customer and deal evidence, and company context. Use when the deliverable is a monetization decision - reviewing a pricing change, planning packaging, deciding whether the company should respond to a competitor price move, or asking what market evidence should inform pricing. Not for a live buyer price objection, a pricing-news briefing, or profiling a competitor whose p

1時間の導入数
1
GitHub Stars
2
更新日
9月28日