1.3万 件 ・ 関連度順
概要と使いどころ
Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Expert Bash help for writing, debugging, and optimizing safe, portable shell one-liners and scripts on macOS/Linux. Use when users ask for Bash or POSIX sh commands, script reviews, ShellCheck fixes, quoting/pipeline issues, process/file automation, or converting requirements into shell scripts.
日本語の概要は準備中です。原文の説明を表示しています。
Complete workflow to commit changes, push to remote, and create a pull request. Use when you want to ship changes end-to-end in one operation, from local changes to an open PR.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to switch AI role/mode/persona or uses role-trigger words such as Captain, Coordinator, 寫文章, 寫文章模式, 文章模式, 技術文章, 部落格, 出版, 預覽. Routes the request to Project Captain, Publishing Director, or Article Writing Mode, loads the matching keep memory when available, and applies the role's workflow without excessive roleplay.
日本語の概要は準備中です。原文の説明を表示しています。
任務卡的必要調整。Use when ATM task cards contain proposal-style notes or dated additive acceptance sections such as 識別/行為/狀態機提案、不重啟驗收、ATM 演進規劃書 v2、連鎖影響、治理補丁, and those notes must be re-analyzed into the formal task-card sections.
日本語の概要は準備中です。原文の説明を表示しています。
Apply the Red-Green-Refactor cycle to software development. Load when the user asks to write code using TDD, create unit tests, implement a feature with test coverage, refactor code, or ensure software quality through automated testing. Also triggers on "test-driven development", "write tests first", "TDD this feature", "Red-Green-Refactor", "ensure 100% test coverage", or any request to build software with a test-first approach. Supports unit, integration, and end-to-end testing strategies.
日本語の概要は準備中です。原文の説明を表示しています。
Security audit orchestrator for agent skills — scans for prompt injection, data exfiltration, credential theft, supply chain risks, and instruction hierarchy violations before any skill is installed, created, improved, or read from a GitHub repo. Load when creating skills from external sources, when improve-skills reads from GitHub repos, when research-skill fetches community SKILL.md files, when a user installs a third-party skill, or when the user asks to audit skill security, scan for injection, check if a skill is safe, scan all skills, or run a security sweep. Orchestrates all secure-* skills in sequence. Content is SAFE only if ALL secure-* skills return SAFE. 36% of community skills contain flaws (Snyk ToxicSkills 2026). This skill is the first line of defense.
日本語の概要は準備中です。原文の説明を表示しています。
Runtime security for agent skills — prevents state corruption, skill overwrite attacks, denial of service, and enforces provenance tracking and no-go repo management. Load as part of the secure-* skill sequence whenever an agent processes external content or writes to the skill store. Also load when the user asks to check for state corruption, prevent skill overwrite, manage no-go repos, check provenance, audit runtime security, detect DoS patterns, or protect the skill store. Covers Issues 6, 9, 10 from the agent security threat model: instruction hierarchy enforcement, state corruption and skill overwrite, and denial of service prevention.
日本語の概要は準備中です。原文の説明を表示しています。
Security checks for repository ingestion — scans repos for poisoned examples, dependency and supply-chain attacks, file/path traversal, format-based attacks, and enforces quarantine-before-commit. Load as part of the secure-* skill sequence whenever an agent reads, ingests, or learns from a GitHub repository. Also load when the user asks to check a repo for poisoned code, scan dependencies, verify supply chain safety, check for path traversal, scan repo files for attacks, or audit a repo before ingestion. Covers Issues 3, 4, 7, 8 from the agent security threat model: poisoned training data, dependency attacks, file/path attacks, and format-based attacks.
日本語の概要は準備中です。原文の説明を表示しています。
Pick a product archetype from a curated catalog before any UI gets built — the single biggest lever for not looking vibecoded. Routes the request to one of B2B-productivity, enterprise-trust, premium-consumer, playful-consumer, editorial, brutalist-distinctive, dev-tool, or marketing-landing, and returns a complete design philosophy: typography pair, color logic, motion curve, density, icon stance, reference sites, and a "feels like X" claim. Load when the user asks to pick an aesthetic, choose a design direction, decide what a UI should feel like, classify a product visually, says "what should this look like", "make this feel like [Linear/Stripe/Apple/Duolingo/...]", "give me a design direction", "what's the right aesthetic for this", or when frontend-design routes here during archetype selection. Sub-skill of frontend-design.
日本語の概要は準備中です。原文の説明を表示しています。
Hard readiness gate before implementation begins — cross-checks the constitution, feature spec, plan, and tasks for consistency, traceability, and unresolved ambiguity. Returns PASS or FAIL with specific findings. Load when the spec-driven-development orchestrator routes /analyze, when the user asks to cross-check spec vs plan, audit traceability, verify spec readiness, gate-check before implementation, or says "is this spec implementation-ready", "trace requirements to tasks", "/analyze", "spec sanity check", "spec readiness gate", "spec consistency check". Output: docs/reviews/YYYY-MM-DD-<slug>-spec-crosscheck.md.
日本語の概要は準備中です。原文の説明を表示しています。
Improve agent reliability over time — diagnose why agents fail and fix the setup. Triggers on: agent keeps failing, same mistake again, agent not improving, make agent smarter, agent quality plateau, agents ignore skills, agent skips tests, fix agent behavior, agent unreliable, improve agent setup, self-improving harness, agents worse over time, tune agent instructions, agent going in circles, agent ignores AGENTS.md, repeated agent errors. Requires harness v0 and eval harness. AUTO-ROUTED from harness-engineering on symptoms. Not first setup — harness-generation first.
日本語の概要は準備中です。原文の説明を表示しています。
Generate 5–10 business idea candidates from a blank page or a founder's domain context — using pain mining, jobs-to-be-done, trend × capability mapping, constraint relaxation, adjacency search, and founder-market-fit prompts. Each candidate is a structured idea card (segment, JTBD, current alternative, why-now, distribution wedge, monetisation, "feels like"). Load when the user asks to generate business ideas, brainstorm startup ideas, find ideas to work on, says "what business should I start", "give me startup ideas", "I don't know what to build", "ideate ventures", "blank-page idea generation", "find me a startup idea", "explore business opportunities". Sub-skill of `venture-exploration`. Hard-bans "Uber for X" / "AI for X" with no specific JTBD, "everyone" segments, and idea cards missing any of the 7 required fields. Does NOT design or evaluate ideas generated — for that use `idea-evaluation`.
日本語の概要は準備中です。原文の説明を表示しています。
Write concise next-agent handoff summaries across sessions, tools, and coding agents. Load when the user says handoff, next agent should know, save context, summarize where we are, switching agents, before ending a meaningful session, or when the user asks to commit, push, commit and push, create a git commit, push to origin, or publish commits — commit/push requests MUST run this skill first to prepare handoff docs, then proceed with git operations.
日本語の概要は準備中です。原文の説明を表示しています。
Build GSAP JavaScript animations for web apps — timelines, scroll-driven motion, SVG draw/morph/path effects, and React integration with useGSAP. Load when the user asks to animate with GSAP, add ScrollTrigger, draw SVG paths with GSAP, morph SVG shapes, sequence page animations, or wire GSAP in React/Next/Vue. Also triggers on "GSAP timeline", "DrawSVG", "MotionPath", "gsap.context", or "scroll animation library". Not for self-contained README/GitHub SVG files.
日本語の概要は準備中です。原文の説明を表示しています。
Measure, profile, and fix performance bottlenecks — Core Web Vitals, backend latency, bundle size, and database queries. Load when performance requirements exist, users report slowness, profiling reveals bottlenecks, or the user asks to optimize load time, LCP, INP, CLS, or response time. Not for premature optimization without evidence. Pairs with browser-testing-with-devtools and ci-cd-and-automation for regression guards.
日本語の概要は準備中です。原文の説明を表示しています。
Mirror issues and status across issue trackers with stable external-ID mapping to avoid duplicates. Load when syncing GitHub and Linear issues, mirroring ticket status, or keeping two trackers in sync. Also triggers on "issue sync", "sync issues", "mirror issues to", "keep Linear and GitHub in sync", or bidirectional issue tracker updates. Requires API access on both sides — stops if credentials missing.
日本語の概要は準備中です。原文の説明を表示しています。
Author pull requests with intent-separated commits, blast-radius disclosure, and verification evidence. Load when opening a PR, writing a PR description, separating refactor from feature commits, or summarizing a change set for review. Also triggers on "write the PR", "PR body", "intent-separated commits", "split refactor from feature", "pr summary", or after safe-change cycles complete. Extends git-workflow-and-versioning — does not replace it.
日本語の概要は準備中です。原文の説明を表示しています。
Tactical fast path: turn a small problem, bug report, edit request, or narrow refactor into three deliverables — a brief change-spec (docs/specs/), a detailed implementation-ready plan (docs/plans/), and a TODO.md with agent-pickable tasks and milestones. Load when the user describes a tactical problem and wants quick planning artifacts, says "plan this change", "create a TODO", "write a plan for this", "problem to plan", "break this into tasks for agents", "I want to change X — plan it", or when process-decomposer routes here after determining the user needs lightweight planning deliverables. Also triggers on "create tasks from this problem", "make this actionable", or "turn this into a plan agents can execute". For feature-sized work that needs an executable spec + constitution + cross-check gate, route to `spec-driven-development` (or `feature-spec`) instead.
日本語の概要は準備中です。原文の説明を表示しています。
Guided first-run that produces a real verified win in under five minutes using the skill library on a seeded offline fixture. Load when a new user asks how to start, run the demo, try agent-loom, or get a quick win. Also triggers on "quickstart", "first run", "demo agent-loom", "try the skills", or onboarding to the library. Zero external credentials required. Idempotent — safe to run multiple times.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate one or more thinking frameworks to work through any problem, decision, document, or idea rigorously. Diagnoses which frameworks fit — inversion, pre-mortem, assumption-mapping, socratic, adversarial-hat — then guides the user through them in the right sequence. Load when the user asks for deep thinking, says "help me think through this properly", "apply your best thinking frameworks", "I need to think carefully before deciding", or "what thinking tools should I use here". Also the entry point for any complex problem where the right framework is unclear. Covers product decisions, engineering tradeoffs, personal decisions, strategy, creative challenges — any domain.
日本語の概要は準備中です。原文の説明を表示しています。
Quickly understand an unfamiliar codebase or project by mapping its architecture, identifying key components and data flows, and surfacing complexity hotspots. Load when the user asks to understand a repo, explain how something works, map the architecture, onboard to a codebase, or explore how components connect. Also triggers on "walk me through this codebase", "how does this project work", "explain the architecture", "what does this repo do", "show me the structure", "onboard me", or any request to build a mental model of a codebase before making changes.
日本語の概要は準備中です。原文の説明を表示しています。
Design state-of-the-art multi-agent systems, orchestration patterns, and wiring from scratch. Load when the user asks to build an agent system from scratch, design agent orchestration patterns, choose between sequential/parallel/hierarchical workflows, or define how multiple agents should collaborate. Also triggers on "agent architecture", "multi-agent wiring", "agent orchestration pattern", "how to connect these agents", "design the communication structure". Called by agent-builder for complex topologies (>4 agents or hierarchical). For process-driven agent design, use agent-builder instead.
日本語の概要は準備中です。原文の説明を表示しています。
Write the executable feature specification — the WHAT and WHY artifact that agents and reviewers treat as source of truth. Owns both /specify and /clarify modes. Load when the user asks to write a feature spec, write a specification, write an executable spec, define functional requirements, capture acceptance criteria as Given/When/Then, or when the spec-driven-development orchestrator routes here. Also triggers on "feature spec", "executable spec", "/specify", "/clarify", "write the spec for this feature", "specification for", "spec-driven", "machine-readable spec". Output: docs/specs/YYYY-MM-DD-<slug>-feature-spec.md. Hard gate: cannot Approve while [NEEDS CLARIFICATION] markers remain.
日本語の概要は準備中です。原文の説明を表示しています。