6,704 件 ・ 人気順
概要と使いどころ
Create comprehensive HTML architecture diagrams showing data flows, business objectives, features, technical architecture, and deployment. Use when users request system architecture, project documentation, high-level overviews, or technical specifications.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from "Solving a Million-Step LLM Task with Zero Errors" (Meyerson, Paolo, Dailey, Shahrzad, Francon, Hayes, Qiu, Hodjat, Miikkulainen — arXiv:2511.09030). Use when designing long-horizon, multi-step agentic LLM pipelines that need very high reliability, applying Maximal Agentic Decomposition (MAD), first-to-ahead-by-k voting, or red-flagging error correction, estimating cost/reliability scaling laws for multi-agent systems, or studying Massively Decomposed Agentic Processes (MDAPs).
日本語の概要は準備中です。原文の説明を表示しています。
Use for authorized cloud, container, and Kubernetes security assessment including metadata SSRF, IAM misconfig, container escape paths, and cluster RBAC review.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating new skills, editing existing skills, or verifying skills work before deployment
日本語の概要は準備中です。原文の説明を表示しています。
Your climate and energy brain trust. 25 named personas across 7 cells covering energy transition, carbon markets, climate modeling, sustainability, grid infrastructure, environmental policy, and ESG.
日本語の概要は準備中です。原文の説明を表示しています。
Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams, document system architecture, visualize software structure, or generate context/container/component/deployment diagrams.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a Disaster Recovery plan with RTO/RPO targets. Use when someone asks to "create a DR plan", "disaster recovery", "business continuity", or "RTO RPO". Do NOT use for step-by-step restoration runbooks — use /pmstudio-recovery instead. Designed for SaaS platform products where Coco Inc is the customer — focuses on service continuity, data recovery, and vendor dependency management rather than infrastructure rebuild.
日本語の概要は準備中です。原文の説明を表示しています。
Speech-to-text transcription via OpenAI Whisper. Supports two modes — Local CLI (no API key, runs on-device) and Cloud API (fast, scalable, requires OPENAI_API_KEY). Use when the user needs to transcribe audio files, translate speech, or convert audio to text.
日本語の概要は準備中です。原文の説明を表示しています。
Use when calling callable functions (httpsCallable), passing data to server-side logic, handling function errors/timeouts, configuring regions, or testing with the Emulator Suite.
日本語の概要は準備中です。原文の説明を表示しています。
Use when setting up Firestore, designing schemas, doing CRUD, creating listeners, paginating queries, configuring indexes, enabling offline persistence, or writing security rules.
日本語の概要は準備中です。原文の説明を表示しています。
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays. Takes the one card the standup marked next and turns it into a reviewable change on a branch, never a deployment. It reads the project's own rules and docs first, makes the smallest change the card describes, runs that project's own gate, writes a change brief with the rollback in one line, and pushes the branch for the member to merge. It never merges, never deploys, never applies a migration, and never rotates a key.
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays. Checks every project in the inventory from the outside, records one dated observation per project, then reads the production log surfaces since its own cursor and groups every error into a fingerprint so a hundred sightings are one incident. It appends the health ledgers, writes the health digest, and cards the incidents that clear the threshold. It changes nothing, deploys nothing, and never rotates a key.
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays, file work only, no browser at all. Reads every ledger and run record since its cursor, resolves which drafted changes actually merged by reading the commit graph rather than a dashboard, closes and reopens incidents on that evidence, folds the card inbox, re-renders the review board, and writes the short morning brief the member opens first. It never merges, never deploys, and never touches a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Weekly, file work only, no browser at all. Reads everything the week produced, picks exactly three moves, and argues both sides of each one before the member reads a word of it, with every clause carrying a number or an observation from a file it names. It argues against its own top recommendation last, records a predicted effect and the metric that would show it so the monthly review can score it, and files each move onto the register. It sends only where you released the channel, spends only where you released it, never deploys, and never touches a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Safely inspect and modify local Avibe configuration, routing, runtime settings, watches, scheduled tasks, Avibe Cloud remote access, and operational state. Also use it to report an Avibe bug, send product feedback, or file a feature request from the current conversation.
日本語の概要は準備中です。原文の説明を表示しています。
Infrastructure as Code patterns (Terraform, Kubernetes), observability design (SLOs, metrics, alerting, dashboards), and pipeline security stages. Load when designing infrastructure, observability, or security scanning.
日本語の概要は準備中です。原文の説明を表示しています。
Monitoring, observability, operational procedures, CI/CD lessons learned, and quality gate definitions. Load when assessing production readiness or validating operational excellence.
日本語の概要は準備中です。原文の説明を表示しています。
CI/CD pipeline design methodology, deployment strategies, GitHub Actions patterns, and branch/release strategies. Load when designing pipelines or deployment workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Rollback procedures, risk assessment, pre/post-deployment validation, and contingency planning. Load when orchestrating deployment or preparing rollback plans. For deployment strategy details (canary, blue-green, rolling), see `cicd-and-deployment` skill.
日本語の概要は準備中です。原文の説明を表示しています。
Designs CI/CD pipelines, infrastructure, observability, and deployment strategy. Use when preparing platform readiness for a feature.
日本語の概要は準備中です。原文の説明を表示しています。
Dung khi can theo doi lien tuc nguoi ta noi gi ve thuong hieu, doi thu va nganh tren mang xa hoi — bo tu khoa giam sat, phan loai sac thai, bao cao tuan va thang, canh bao som, chi so brand health. Kich hoat khi user nhac 'social listening', 'theo doi thuong hieu', 'giam sat mang xa hoi', 'brand monitoring', 'khach dang noi gi ve minh', 'do sentiment', 'co ai nhac ten shop khong', 'canh bao som khung hoang'. Khong dung cho — khung hoang DA XAY RA va can xu ly ngay thi dung skill 66-crisis-playbook; mo xe chien luoc mot doi thu cu the thi dung skill 08-nghien-cuu-doi-thu; doc so lieu ads va web thi dung skill 13-phan-tich-du-lieu.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a brand faces a communications CRISIS or a campaign is failing in public — L1 to L5 severity classification, a first-four-hours process, response templates by type, an escalation matrix, a do-not-do list, holding statements, and a post-mortem. Trigger on 'PR crisis', 'crisis playbook', 'a complaint is going viral', 'bad reviews are spreading', 'our content caused backlash', 'we are getting attacked online'. Also use when the user forwards an angry thread and asks what to do right now. Not for — monitoring before anything blows up, see `15-social-listening-global`; diagnosing weak performance numbers, see `03-performance-eval-global`; the routine post-campaign review, see `63-campaign-retrospective-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a leader evaluates a marketing TEAM MEMBER using data — a KPI scorecard by role, strengths with real examples, areas to improve stated as observable behavior, a 30 and 90 day development plan, and a 1-5 rating rubric. Trigger on 'performance review for my marketer', 'evaluate a team member', 'monthly 1:1 review', 'feedback for my content writer', 'development plan for an employee', 'is this person underperforming'. Also use when the user is unhappy with someone and cannot articulate why. Not for — evaluating a campaign rather than a person, see `63-campaign-retrospective-global`; reviewing one piece of output, see `62-marketing-review-global`; scoring an external vendor, see `67-agency-vendor-brief-global`.
日本語の概要は準備中です。原文の説明を表示しています。