「research」の検索結果

Pointer to the upstream skill for behavioural guidelines that reduce common LLM coding mistakes, installed from upstream.

日本語の概要は準備中です。原文の説明を表示しています。

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

日本語の概要は準備中です。原文の説明を表示しています。

Use when designing a new REST or GraphQL API, reviewing an API spec before implementation, setting team API standards, or migrating REST to GraphQL. Covers resources, HTTP semantics, pagination, error handling, and pitfalls.

日本語の概要は準備中です。原文の説明を表示しています。

Use when you have a written implementation plan to execute in a separate session with review checkpoints

日本語の概要は準備中です。原文の説明を表示しています。

Install, update, version-check, or uninstall the Coco open-source AI workflow framework via bin/coco.js. Use when setting up Coco on a machine, checking out the pinned release tag into an existing clone, checking the installed version, or removing it. npx cocosuperintelligence is the published path (clones the pin and installs). Triggers on "install coco", "update coco", "set up coco", "coco cli", "uninstall coco".

日本語の概要は準備中です。原文の説明を表示しています。

Wrap any command-line tool into a JSON-emitting agent skill. Use when you want to make a CLI reliably callable and parseable by an AI agent — introspect its --help, define a structured-output (--json) contract and a stable error contract, then generate a SKILL.md wrapper with verified examples. Triggers on "wrap this CLI", "make X agent-usable", "generate a skill for this command", "turn a tool into an agent skill".

日本語の概要は準備中です。原文の説明を表示しています。

Use when building AI features into a product: LLM integration, RAG pipelines, guardrails, streaming, AI UX, prompt engineering, or AI cost control. Treats prompts as code and validates every model output.

日本語の概要は準備中です。原文の説明を表示しています。

Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers queries against the corpus, lints the graph for health, and audits in-context human feedback filed from Obsidian or the local web viewer. Use when (1) scaffolding a new knowledge base for any research topic, (2) ingesting articles/papers/PDFs/web pages into raw/, (3) compiling or restructuring wiki articles from existing raw material, (4) answering questions against the wiki and filing durable answers back, (5) running lint passes for dead links / orphan pages / coverage gaps / audit shape, (6) processing human feedback from the audit/ directory and applying corrections. Not for general note-taking, daily journals, or non-wiki Obsidian use.

日本語の概要は準備中です。原文の説明を表示しています。

Find web sources with query-relevant page excerpts and optional full-page content, and discover workflows, data APIs, and indexes. Use for web research or finding structured records, listings, transcripts, and datasets. Supports semantic tool discovery, domain matching, and progressive catalogue browsing.

日本語の概要は準備中です。原文の説明を表示しています。

Runs once by hand on the first day and once a month after that. On the first run it researches the business from its own public surfaces, reads the member's own already published posts, and builds the voice file from real samples rather than from an idea of a voice, then writes the plan, creates the proof inventory, seeds the opening slots, and registers the recurring jobs. On every monthly run it re reads the evidence the kit produced and rebuilds only what the evidence contradicts. It publishes only where you released the channel, never replies, spends only where you released it, and it never enters a credential.

日本語の概要は準備中です。原文の説明を表示しています。

Runs once by hand on the first day and once a month after that, on the first weekday, light browser lane. On the first run it researches the business from its own public surfaces before asking anything, writes the strategy folder, seeds the pipeline, reconciles the schedule table, and registers the recurring jobs. On every monthly run it re-reads the evidence the kit produced, applies what changed to the files it owns, and carries every member written setting across verbatim. It holds every outbound action unless you released the channel, and it never enters a credential.

日本語の概要は準備中です。原文の説明を表示しています。

Runs once by hand on the first day and once a month after that, light browser lane. On the first run it researches the business from its own published surfaces before asking anything, writes the strategy folder, creates the ledgers, seeds the opening cards, builds the single page dashboard, reconciles the schedule table, and registers the eight recurring jobs. On every monthly run it re-reads a month of the kit's own evidence, applies what changed, adds a tab for a channel that gained volume, rebuilds, and reconciles every registered job against the table. It holds every outbound action unless you released the channel, and it never enters a credential.

日本語の概要は準備中です。原文の説明を表示しています。

Runs once by hand on the first day and once a month after that. On the first run it researches the business from its own public surfaces before asking anything, writes the strategy folder, seeds the launch board, builds the tailored command center, reconciles the schedule table, and registers the recurring jobs. On every monthly run it re-reads the evidence the kit produced, applies what changed, reconciles drift, and rebuilds. It holds every outbound action unless you released the channel, and it never enters a credential.

日本語の概要は準備中です。原文の説明を表示しています。

Weekdays, browser only when the card needs one. Takes the next ready cards off the launch board and does the work each one names: stages copy into the dashboard, fills a directory or press form and leaves it open in its tab, verifies a setup, packages a handoff, or researches its own next targets. It ticks its own card the moment it has verified the file that closes it. It submits only where you released the channel, sends only where you released the channel, spends only where you released it, and never touches a credential.

日本語の概要は準備中です。原文の説明を表示しています。

Runs once by hand on the first day and once a month after that. On the first run it researches the business from its own public presence, writes the charter with a source and a date beside every conclusion, discovers the AI Employees actually installed on this machine within a bounded search, writes the map every other routine in this kit reads, seeds the priorities and the watchlist once, builds the fleet dashboard, and registers this Employee's own seven jobs. On every monthly run it re-runs discovery and reconciles the map against what is really there. It never writes into another Employee's folder, never registers a job it does not own, sends only where you released the channel, spends only where you released it, and never touches a credential.

日本語の概要は準備中です。原文の説明を表示しています。

Runs once by hand on the first day and once a month after that. On the first run it researches the business from its own public surfaces before asking anything, reads the account structure once, writes the plan folder, seeds the board, creates the creative doctrine, builds the dashboard, and registers the recurring jobs. It asks about exactly two things, the monthly ceiling and the daily cap, because those are the two numbers that decide how much money can leave. On every monthly run it re reads the evidence, corrects what the ledgers prove wrong, and reconciles drift.

日本語の概要は準備中です。原文の説明を表示しています。

Weekly, browser only when a source refuses to be fetched. Counts unpublished calendar entries per property by folding the published ledger against the calendar, and where every property is above its runway threshold it records the counts and exits, which is the normal run. Where a property is low it researches the next block from rank evidence, the topic map, and live result sets, refuses any keyword already targeted, and appends fully specified entries after the last existing block. It is the only writer of the calendar and it never modifies, reorders, or renumbers an existing entry.

日本語の概要は準備中です。原文の説明を表示しています。

Generate clinical trial protocols for medical devices or drugs. This skill should be used when users say "Create a clinical trial protocol", "Generate protocol for [device/drug]", "Help me design a clinical study", "Research similar trials for [intervention]", or when developing FDA submission documentation for investigational products.

日本語の概要は準備中です。原文の説明を表示しています。

Critique dimensions and scoring for research document reviews

日本語の概要は準備中です。原文の説明を表示しています。

Tool safety protocols, adversarial output validation, error recovery patterns, and I/O contracts for research operations

日本語の概要は準備中です。原文の説明を表示しています。

Generates 3-5 divergent design directions through JTBD analysis, competitive research, structured brainstorming, and taste evaluation before convergence. Use when the team has a validated problem but hasn't chosen a solution approach.

日本語の概要は準備中です。原文の説明を表示しています。

Review criteria for the nw-diverger-reviewer — validates JTBD rigor, research quality, option diversity, taste application correctness, and recommendation coherence in DIVERGE wave artifacts

日本語の概要は準備中です。原文の説明を表示しています。

Canonical AT completeness gate — research-anchored 7-category taxonomy (C1-C7) + 15-item mechanical checklist. Paradigm-neutral. Drives acceptance-designer reviewer verdict deterministically.

日本語の概要は準備中です。原文の説明を表示しています。

Best practices for command definition files - size targets, declarative template, anti-patterns, and canonical examples based on research evidence

日本語の概要は準備中です。原文の説明を表示しています。