AGENT SKILLS · ミッション装備
実際に使われている Agent Skills
公開リポジトリの検証済み Skills を比較し、機能、内容、導入状況、出典を確認してから追加できます。
- 掲載範囲
- 検証済み
- Skills
- 22,719
- リポジトリ
- 3485
- 最終同期
- 2026/10/31
sylphxaigovern-enterprise-access
Govern who may grant, inherit, exercise, review, recover, and revoke administrative authority across customer tenants. Use when identity-provider assertions are inputs to product permission, not a substitute for it.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaihandoff-work
Safely persist in-progress state and write an actionable resumption brief for another machine, session, or developer. Use when handing off work, switching computers or workspaces, pausing mid-task, saving work-in-progress across environments, or transferring an unfinished objective. Also use to write a short status, decision, or incident update that leads with the outcome. Do not use for fully completed deliverables ready to merge (use drive-to-delivery), or production cutovers (use execute-hard
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaiimplement-continuous-integration
Build or slim a repository's required commit build around fast product-behavior checks. Use when CI is slow, flaky, duplicated, or blocking on prose, naming, or file-layout linters, or when the user asks what should be required on every PR. Do not use for CD, release trains, or incident response.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaimaintain-product
Repair a product defect or regression at its owning layer. Use for live or dogfood failures, flaky paths, and current user harm. Do not use to finish or polish an already integrated product.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaimarketplace-trust-operations
Assess marketplace trust operations — policy, evidence, enforcement, appeals, risk queues, and trust economics. Use when the user asks to review marketplace moderation, seller enforcement, risk scoring, or appeal flows. Do not use to design the enforcement system.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaimigrate-customer-data
Migrate customer data so meaning, ownership, access, and history survive. Use when acceptance is preserved semantics, not row-count equality. Do not use for the authority switch of a live writer.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaimodel-product-abuse-risk
Model product abuse and a least-harm control ladder. Use when attackers, fraud, or policy evasion can take money, access, or other users' work. Do not publish an exploitation recipe.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxainotification-strategy
Assess a notification strategy — stop conditions, cooldowns, cadence, quiet hours, and suppression. Use when the user asks to review notifications, push strategy, or messaging cadence. Do not use to design the notification system.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaioperate-customer-support
Design or improve the support operating model: contact taxonomy, routing, waiting-state clocks, authority, and quality loops. Use for the system, not for answering one ticket.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaioptimize-decision-model
Translate an operational decision into an explicit model — objective, constraints, uncertainty, and a recomputed solution — then stress it for proxy failure. Use when the user asks to optimize, allocate, schedule, or choose under constraints. Do not use to pick the next backlog item, run an experiment, or critique a claim.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaioptimize-store-listing
Create a truthful store or channel listing and creative sequence for install, trial, or purchase. Use for metadata, screenshots, and conversion narrative. Do not use for signing or publishing the binary.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaiprice-saas-subscription
Choose SaaS plan architecture and list prices — value metric, seats vs usage, included amounts, overages, trials, and catalog migration. Use when pricing a product, designing a free tier, picking a meter, or repackaging plans. Do not use for raising an already-live price, or for implementing checkout.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaiproduce-game-2d-map-assets
Produce engine-ready 2D tilesets, prop packs, layered maps, collision metadata, and composed previews. Use when the user asks for tiles, a tilemap, terrain, Tiled/Godot/Unity 2D maps, or seam-checked atlas props. Do not use for character animation sheets or store key art.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaiproduce-game-2d-sprites
Produce engine-ready 2D character, VFX, HUD, and icon sprites, including animation sheets and loop QC. Use when the user asks for a sprite sheet, idle/walk/attack cycle, chroma-key frames, video-to-sprite, or a game atlas. Do not use for map tilesets, 3D models, or marketing screenshots.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaiproduce-product-assets
Produce finished product media and design assets from a current brief and product truth. Use for screenshots, key art, store media, campaign visuals, motion, audio, localization, and accessible variants. Do not use for engine-ready game sprites or tilesets.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaiprototype-product
Run the cheapest real probe that can change a product decision, then kill, continue, or pivot from the observation. Use when the user wants a prototype, spike, or cheap test. A demo without a decision criterion is not this job. Do not use to register a production experiment or to polish an already accepted product.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaiprovision-agent-workspace
Create or attach an isolated filesystem and shell for an agent — host workspace, sandbox, or VM — with explicit network, secret, lifetime, and cost bounds. Use when the user asks to provision a sandbox, code-execution environment, or throwaway VM. Do not use to write application features in an existing repo.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxairecord-structured-deliberation
Structure a multi-participant deliberation and record a decision-ready result — options, strongest reasons, dissent, and the named owner's next action. Use when several perspectives, competing proposals, or material objections need a fair synthesis. Do not use for a single-analyst critique or a domain go/no-go review.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxairesolve-customer-support-case
Resolve one customer support case through a truthful outcome, authorized action, and verified closure. Use for a single ticket, not for designing the support system.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxairun-product-feedback-loop
Cluster support tickets, in-app feedback, and authorized store reviews into owned product work and close the loop with the people who wrote in. Use when triaging feedback, mining reviews, or asking what customers said after a launch. Do not use to answer one ticket.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaiselect-next-work
Select and claim the next high-value work item from current product and repository state. Use when the user wants the agent to choose from an existing backlog. Do not use to finish an already accepted objective.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaiui-flow
Design or implement one product UI flow with loading, empty, error, and success states, verified on a real render. Use when the user asks to build a screen, fix a form, design a flow, or match an existing design system. Do not use to review an existing flow, extract a design system, or produce store screenshots.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
zzcigitea
Operate a Gitea instance via its REST API at /api/v1/... with curl. FORCED ROUTING — use this skill for any repository whose git remote host is not github.com: derive the candidate HTTPS base URL from the remote host, probe /api/v1/version, then call the REST endpoints directly.
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月13日
crontapcrontap-recurring-agent-endpoint
Schedule an HTTP endpoint that a deployed application uses to start its own agent workflow, then monitor completion with a heartbeat. Use when a user has an application-owned agent runtime that needs a durable external clock.
- 1時間の導入数
- 1
- GitHub Stars
- 1
- 更新日
- 9月16日