2,344 件 ・ 関連度順
概要と使いどころ
Startup skill router: maps any incoming request to the correct skill using Quick Lookup table and _manifest.json. Loaded automatically at session start. Triggers on: every new request — this is the dispatch layer, not a user-facing skill. NOT for: executing tasks directly — always routes to a domain-specific skill.
日本語の概要は準備中です。原文の説明を表示しています。
MANDATORY parallel execution patterns, cluster overview script, -o json with jq filtering, batch operations, and common pitfalls
日本語の概要は準備中です。原文の説明を表示しています。
Poll RSS, JSON APIs, and GitHub with watermark dedup.
日本語の概要は準備中です。原文の説明を表示しています。
Hand-drawn Excalidraw JSON diagrams (arch, flow, seq).
日本語の概要は準備中です。原文の説明を表示しています。
Plan and prepare an OpenAmer-specific fine-tune from the collected brain data: data curation, ChatML JSONL, training, evaluation. 'The organism becomes its own brain'.
日本語の概要は準備中です。原文の説明を表示しています。
Vollständige Dokumentation des OpenAmer Plugin-API-Systems. Hooks, Events, Lifecycle, manifest.json Format, Config-Integration und Plugin-Manager.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Trigger only when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for example: orphaned sensitive code, security maintainers, CODEOWNERS reality checks for risk, sensitive hotspots, or ownership clusters). Do not trigger for general maintainer lists or non-security ownership questions.
日本語の概要は準備中です。原文の説明を表示しています。
Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries for plugin ordering and availability metadata, or update an existing local plugin during development with the CLI-driven cachebuster and reinstall flow.
日本語の概要は準備中です。原文の説明を表示しています。
MongoDB schema design patterns and anti-patterns. Use when designing data models, reviewing schemas, migrating from SQL, or troubleshooting performance issues caused by schema problems. Triggers on "design schema", "embed vs reference", "MongoDB data model", "schema review", "unbounded arrays", "one-to-many", "tree structure", "16MB limit", "schema validation", "JSON Schema", "time series", "schema migration", "polymorphic", "TTL", "data lifecycle", "archive", "index explosion", "unnecessary indexes", "approximation pattern", "document versioning".
日本語の概要は準備中です。原文の説明を表示しています。
Track and visualize ML training experiments with Trackio. Use when logging metrics during training (Python API), firing alerts for training diagnostics, or retrieving/analyzing logged metrics (CLI). Supports real-time dashboard visualization, alerts with webhooks, HF Space syncing, and JSON output for automation.
日本語の概要は準備中です。原文の説明を表示しています。
Detects MSBuild projects with conflicting OutputPath or IntermediateOutputPath. Only activate in MSBuild/.NET build context. USE FOR: builds failing with 'Cannot create a file when that file already exists', 'The process cannot access the file because it is being used by another process', intermittent build failures that succeed on retry, missing outputs in multi-project builds, multi-targeting builds where project.assets.json conflicts. Diagnoses when multiple projects or TFMs write to the same bin/obj directories due to shared OutputPath, missing AppendTargetFrameworkToOutputPath, or extra global properties like PublishReadyToRun creating redundant evaluations. DO NOT USE FOR: file access errors unrelated to MSBuild (OS-level locking), single-project single-TFM builds, non-MSBuild build systems. INVOKES: binlog MCP server tools (overview, projects, evaluations, properties, double_writes); falls back to dotnet msbuild binlog replay + grep when the MCP is unavailable.
日本語の概要は準備中です。原文の説明を表示しています。
Validates custom dotnet new templates for correctness before publishing. Catches missing fields, parameter bugs, shortName conflicts, constraint issues, and common authoring mistakes that cause templates to fail silently. USE FOR: checking template.json files for errors before publishing or testing, diagnosing why a template doesn't appear after installation, reviewing template parameter definitions for type mismatches and missing defaults, finding shortName conflicts with dotnet CLI commands, validating post-action and constraint configuration. DO NOT USE FOR: finding or using existing templates (use template-discovery), creating projects from templates (use template-instantiation), creating templates from existing projects (use template-authoring).
日本語の概要は準備中です。原文の説明を表示しています。
Get reliable JSON, enums, and typed objects from LLMs using response_format, tool_use, and schema-constrained decoding across OpenAI, Anthropic, and Google APIs.
日本語の概要は準備中です。原文の説明を表示しています。
Set up the current project folder for AOS: slug, wiki, memory, Synapse map, AGENTS.md. Generated from plugin-commands.json; invoke as $bdb-aos:init.
日本語の概要は準備中です。原文の説明を表示しています。
Brainstorm a topic with the matching skill: bdbrainstorm, bdbmediastorm for event tech, grill-me for a stress test. Generated from plugin-commands.json; invoke as $bdb-aos:brainstorm.
日本語の概要は準備中です。原文の説明を表示しています。
Check the machine and the current project, and print suggested permissions.allow entries without writing any settings. Generated from plugin-commands.json; invoke as $bdb-aos:doctor.
日本語の概要は準備中です。原文の説明を表示しています。
Plan end to end: draft, render in plan-canvas or Plan Builder, annotate, await approval, then hand off. Generated from plugin-commands.json; invoke as $bdb-aos:plan.
日本語の概要は準備中です。原文の説明を表示しています。
Run the startcycle-graph pipeline: durable state, repair loop, quality gate, escalation. Generated from plugin-commands.json; invoke as $bdb-aos:graph.
日本語の概要は準備中です。原文の説明を表示しています。
Bring this machine to a complete, verified AOS installation (skills, MCP servers, gate hooks, memB, OpenWiki, Synapse). Generated from plugin-commands.json; invoke as $bdb-aos:setup.
日本語の概要は準備中です。原文の説明を表示しています。
Query or store long-term memory with memB. Generated from plugin-commands.json; invoke as $bdb-aos:memb.
日本語の概要は準備中です。原文の説明を表示しています。
Start a new composition: project init, brainstorm, then ask whether graph or startcycle follows. Generated from plugin-commands.json; invoke as $bdb-aos:startproject.
日本語の概要は準備中です。原文の説明を表示しています。
Run a prompt repeatedly on an interval, using the harness built-in plus loop templates. Generated from plugin-commands.json; invoke as $bdb-aos:loop.
日本語の概要は準備中です。原文の説明を表示しています。
Supervise other Claude Code sessions on this machine: roster, status requests, GO board, idle notices. Generated from plugin-commands.json; invoke as $bdb-aos:mastersession.
日本語の概要は準備中です。原文の説明を表示しています。
Drive a whole tdmcp feature BACKLOG to completion as resumable, wave-by-wave releases — the campaign layer ABOVE tdmcp-pipeline/tdmcp-feature-lead. Use whenever the user wants to implement an ENTIRE backlog or discovery file (e.g. _workspace/discovery*/FEATURE_BACKLOG*.md), 'all the features', many features across multiple releases, or a long autonomous build campaign, AND for every follow-up: continue/resume the campaign, run the next wave, re-run a failed wave, fold in QA results, or check campaign status. Backed by a ledger.json so re-running is idempotent (skips shipped work, resumes interrupted work) and resilient (retry-once then quarantine-and-continue). For a SINGLE feature or one small batch, use tdmcp-pipeline instead; this skill is for the whole ledger.
日本語の概要は準備中です。原文の説明を表示しています。