1,257 件 ・ 関連度順
概要と使いどころ
Install, verify, and operate mdoctor on macOS and Debian/Arch-based Linux. Use when users ask to set up mdoctor, install dependencies, test branch builds on the current machine, run first health checks, troubleshoot install/runtime issues, or perform safe cleanup/fix workflows with mdoctor commands.
日本語の概要は準備中です。原文の説明を表示しています。
Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.
日本語の概要は準備中です。原文の説明を表示しています。
Use when about to claim work is complete, fixed, or passing — requires running verification commands and confirming output before making any success claims. Evidence before claims, always.
日本語の概要は準備中です。原文の説明を表示しています。
Utility — fill the surface stack map in tech-stack.md and provision skills using intelligent resolution. Called by pipeline commands when tech stack info changes.
日本語の概要は準備中です。原文の説明を表示しています。
Automate recruiting and hiring workflows in Ashby -- manage candidates, jobs, applications, interviews, and notes through natural language commands.
日本語の概要は準備中です。原文の説明を表示しています。
Create, revise, or audit AGENTS.md files from repository evidence, verified commands, and correctly scoped instructions without overwriting maintainer intent.
日本語の概要は準備中です。原文の説明を表示しています。
REQUIRED --repo flag for all commands, helper functions for code review comments, suggestion block syntax rules
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Ansible — ansible automation and configuration management. Covers playbook execution, inventory management, role management, vault secrets, ad-hoc commands, fact gathering, and task debugging. Use when running playbooks, managing inventories, debugging task failures, or auditing Ansible configurations.
日本語の概要は準備中です。原文の説明を表示しています。
Use for OpenAmer central CLI Commander with 28 subcommands.
日本語の概要は準備中です。原文の説明を表示しています。
Run verification commands and confirm output before claiming success
日本語の概要は準備中です。原文の説明を表示しています。
Train and fine-tune transformer language models using TRL (Transformers Reinforcement Learning). Supports SFT, DPO, GRPO, KTO, RLOO and Reward Model training via CLI commands.
日本語の概要は準備中です。原文の説明を表示しています。
Zero-config Postgres for Netlify apps via @netlify/database — querying data from Functions/Edge Functions, writing schema migrations, setting up Drizzle ORM, local dev with netlify dev, database branches for deploy previews, and migrating an existing Postgres project onto Netlify. Use when adding a database, building a contact form or CRUD API, writing SQL migrations, wiring up Drizzle, running netlify database commands, testing with a local Postgres, or switching from Neon/Supabase/RDS to Netlify Database.
日本語の概要は準備中です。原文の説明を表示しています。
Generate MSBuild binary logs (binlogs) for build diagnostics and analysis. Only activate in MSBuild/.NET build context. USE FOR: adding /bl:{} to any dotnet build, test, pack, publish, or restore command to capture a full build execution trace, prerequisite for binlog-failure-analysis and build-perf-diagnostics skills, enabling post-build investigation of errors or performance. Requires MSBuild 17.8+ / .NET 8 SDK+ for {} placeholder; PowerShell needs -bl:{{}}. DO NOT USE FOR: non-MSBuild build systems (npm, Maven, CMake), analyzing an existing binlog (use binlog-failure-analysis instead). INVOKES: shell commands (dotnet build /bl:{}).
日本語の概要は準備中です。原文の説明を表示しています。
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).
日本語の概要は準備中です。原文の説明を表示しています。
Browse and preview AOS skills, agents and playbooks in the local store UI. Generated from plugin-commands.json; invoke as $bdb-aos:store.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate parallel coding agents across repositories through the AO daemon. Generated from plugin-commands.json; invoke as $bdb-aos:orchestrator.
日本語の概要は準備中です。原文の説明を表示しています。
Pre-ship framing and the technical release gate, with approvals under the go-gate rules. Generated from plugin-commands.json; invoke as $bdb-aos:shipping.
日本語の概要は準備中です。原文の説明を表示しています。
Search, scrape, and interact with the web via the Firecrawl CLI. Use this skill whenever the user wants to search the web, find articles, research a topic, look something up online, scrape a webpage, grab content from a URL, get data from a website, crawl documentation, download a site, or interact with pages that need clicks or logins. Also use when they say "fetch this page", "pull the content from", "get the page at https://", or reference external websites. This provides real-time web search with full page content and interact capabilities — beyond what Claude can do natively with built-in tools. Do NOT trigger for local file operations, git commands, deployments, or code editing tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Run the startcycle-graph pipeline: durable state, repair loop, quality gate, escalation. Generated from plugin-commands.json; invoke as $bdb-aos:graph.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Survey the whole tdmcp project and produce a prioritized list of NEW features it could implement — across artist controls, CLI/DX, AI/LLM integration, and TouchDesigner depth. Use whenever the user wants to brainstorm, discover, survey, list, or audit what features/tools/effects/controls/commands/prompts/capabilities tdmcp *could* add, asks 'what could we build / what's missing / what are the opportunities / ideas for the project', or wants a feature backlog or gap analysis. Also for follow-ups: re-run, refresh, update, re-survey, deepen, or re-prioritize the backlog, or survey just one surface (e.g. 'CLI ideas only'). This is the IDEATION harness — it produces a list to decide from; it does NOT build. When the user has already chosen a feature and wants it implemented/shipped/added, use tdmcp-pipeline instead.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
List all pb-* playbooks with duration, difficulty and requirements, and start one. Generated from plugin-commands.json; invoke as $bdb-aos:playbooks.
日本語の概要は準備中です。原文の説明を表示しています。