3,019 件 ・ 関連度順
概要と使いどころ
Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising. Use when the user wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized, investor-facing messaging.
日本語の概要は準備中です。原文の説明を表示しています。
Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing. Informed by quality engineers with 15+ years experience across FDA, IATF 16949, and AS9100 environments. Includes NCR lifecycle management, CAPA systems, SPC interpretation, and audit methodology. Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues.
日本語の概要は準備中です。原文の説明を表示しています。
Codified expertise for electricity and gas procurement, tariff optimization, demand charge management, renewable PPA evaluation, and multi-facility energy cost management. Informed by energy procurement managers with 15+ years experience at large commercial and industrial consumers. Includes market structure analysis, hedging strategies, load profiling, and sustainability reporting frameworks. Use when procuring energy, optimizing tariffs, managing demand charges, evaluating PPAs, or developing energy strategies.
日本語の概要は準備中です。原文の説明を表示しています。
Managing local .NET tools with dotnet-tools.json for consistent tooling across development environments and CI/CD pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
AgentHero AI - Hierarchical multi-agent orchestration system with PM coordination, file-based state management, and interactive menu interface. Use when managing complex multi-agent workflows, coordinating parallel sub-agents, or organizing large project tasks with multiple specialists. All created agents use aghero- prefix.
日本語の概要は準備中です。原文の説明を表示しています。
Patterns for multi-agent coordination, task decomposition, handoffs, and workflow orchestration. Best practices for building and managing agent systems.
日本語の概要は準備中です。原文の説明を表示しています。
Provides the "how-to" for workflow / task execution orchestration. Defines methods for planning multi-phase task/workflows, implementing them through agent delegation, and managing artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Transition from a hands-on "bricklayer" to a high-level "architect" by managing a fleet of autonomous AI agents. Use this when you need to scale engineering output with a small team, handle repetitive migrations/bug fixes, or onboard engineers to complex legacy codebases.
日本語の概要は準備中です。原文の説明を表示しています。
Expert in designing, orchestrating, and managing multi-agent systems (MAS). Specializes in agent collaboration patterns, hierarchical structures, and swarm intelligence. Use when building agent teams, designing agent communication, or orchestrating autonomous workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Expert prompt engineer specializing in designing, optimizing, and managing prompts for large language models. Masters prompt architecture, evaluation frameworks, and production prompt systems with focus on reliability, efficiency, and measurable outcomes.
日本語の概要は準備中です。原文の説明を表示しています。
Agent assignment matrix, blocker escalation, and TDM coordination patterns. Use when assigning work to specialists, managing blockers, or coordinating multi-agent workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Create a new skill for this repository following the agentskills.io specification with proper structure and packaging
日本語の概要は準備中です。原文の説明を表示しています。
Use fmail for agent-to-agent messaging with team conventions.
日本語の概要は準備中です。原文の説明を表示しています。
Run deep research on a single competitor. Produces a dossier with executive summary, position + messaging, status-quo alternatives, key differentiators, pricing position, where-they-win / where-they-lose, threat assessment, and what to watch. Writes to marketing/competitors/MMYY-{competitor-slug}.md. Triggers - "competitor research", "competitive analysis", "research competitor X", "battlecard prep", "analyze [competitor name]
日本語の概要は準備中です。原文の説明を表示しています。
VNX feature-execution kickoff preflight. USE THIS when starting or resuming a feature or track from its plan: checking worktree/queue/staging health, finding the first promoteable dispatch, and handing off to @t0-orchestrator. Reads the feature's track + plan doc from Horizon's tracks DB (`vnx horizon`, alias `vnx objective`); the repo FEATURE_PLAN.md/PR_QUEUE.md are generic examples, not the source.
日本語の概要は準備中です。原文の説明を表示しています。
Write high-CTR YouTube and YouTube Shorts titles under 100 characters using 2026 packaging formulas (curiosity-gap, number, how-I outcome, mistake/loss, transformation, versus). Balances curiosity with a real keyword, front-loads the click-deciding words for the 60-char mobile cutoff, and returns 3 to 5 A/B variants tagged by goal for Test and Compare. Use to title or rework a video. Not for the description (use yt-description-writer) or the thumbnail overlay (use yt-thumbnail-brief).
日本語の概要は準備中です。原文の説明を表示しています。
Automatic init the first time Claude acts in an incident or alerts channel — one named like #inc-…, #incident-…, #sev0-…/#sev1-…, or whose recent messages are pages or alerts from PagerDuty, Opsgenie, incident.io, Datadog, Sentry or Grafana, or relayed by people (talk about being paged is not an alert) — that isn't already a team's oncall / monitoring channel. Run once per channel, on first contact (just invited, first @-mention, channel just created), before doing what was asked: load the oncall memory oncall setup wrote to shared workspace memory, pick the owning team's section, work out which monitoring / paging / code tools Claude can reach and which are missing, post one short zero-context message, note findings in this channel's memory, then hand off to `incident-investigate` if something was asked — or immediately, unasked, when the channel was plainly opened for a live outage. Works with no oncall memory (offers setup once). Also on "load the oncall setup here" / "init this incident".
日本語の概要は準備中です。原文の説明を表示しています。
Query and manage PagerDuty — find out who's on call, list and manage incidents, read escalation policies and schedules, trace who got paged and why, acknowledge/resolve/snooze/escalate incidents, and create or update services. Use this whenever the user mentions PagerDuty, on-call, paging, escalation, an incident ID like `PXXXXXX` or `Q...`, asks "who's on call", "page the on-call", "ack this incident", "why wasn't I paged", or pastes a pagerduty.com URL — even if they don't say "API". Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
日本語の概要は準備中です。原文の説明を表示しています。
Core agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you want a strict review of a marketing asset against style rules, factual accuracy, and messaging alignment.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill for any marketing research, product positioning, copywriting research, or audience profiling task. Triggers include: "research my product", "develop my value proposition", "profile my avatar", "understand my market", "create a unique mechanism", "market awareness", "market sophistication", "ideal customer profile", "ICP research", "positioning research", "copywriting research", "features and benefits", "competitor research", "competitive analysis", or any request to deeply research a product or audience for marketing purposes. Use this skill proactively whenever a user wants to prepare materials for sales copy, landing pages, ads, email sequences, or any persuasion-focused content. If a user says "help me understand my market", "I need to figure out my messaging", "who is my customer", or "what makes my product different", this skill applies immediately.
日本語の概要は準備中です。原文の説明を表示しています。
Give your OpenClaw agent a homelab. Use when managing Docker containers, installing marketplace apps, or any Docker-related tasks on behalf of the user. Scope-based API key permissions — agent can only do what the key allows. On Linux, Docker requires sudo — without root access, WAGMIOS is the only safe interface for agent homelab control. Supports multi-machine management — one agent can manage multiple WAGMIOS instances across different hosts, each with its own scoped key. Requires X-API-Key header on every request (user provides at runtime). Includes Docker installation check and startup validation.
日本語の概要は準備中です。原文の説明を表示しています。
Construct and score Grand Slam Offers using the Value Equation — sourced pain mining, dream outcome articulation, problems→solutions→trim-and-stack offer construction, guarantee/scarcity/bonus design, 1-10 scoring on the four Value Equation variables, pricing sanity pass, and compliance check. Use when "build an offer", "grand slam offer", "value equation", "offer stack", "make this offer irresistible", "design a guarantee", "hormozi offer", "why isn't my offer selling", "pricing and packaging for my offer", or any request to design, score, or rework a commercial offer.
日本語の概要は準備中です。原文の説明を表示しています。
Two-layer funnel audit on collected data only — stress-test the awareness layer (hooks, messaging, proof placement, attention leaks on live pages and ads) and the lead-capture layer (opt-ins and lead magnets scored on the four Value Equation variables, friction findings, weakest-magnet rewrite), plus a phone-path check under the Phone Capture Fit Rule. Use when "funnel audit", "audit my funnel", "why is my funnel leaking", "top of funnel isn't converting", "audit our lead magnets", "opt-in audit", "awareness to lead audit", "where are we losing people", "lead capture audit", or any request to diagnose the full awareness-to-lead flow rather than one page.
日本語の概要は準備中です。原文の説明を表示しています。