2,457 件 ・ 関連度順
概要と使いどころ
Formatting, structure, and execution rules for Quarto markdown documents. Trigger when: - Writing, editing, or rendering Quarto documents, reports, presentations, or websites. - Files matching the pattern **/*.qmd are in the workspace or referenced. - Tasks involve: quarto render, quarto preview, knitr, jupyter. - Prompt contains keywords: quarto, qmd, yaml header, code chunk, callout, cross-reference.
日本語の概要は準備中です。原文の説明を表示しています。
AID Phase 0 - Research & discovery. Use for validating problem spaces, identifying stakeholders, defining success metrics, deciding whether to proceed.
日本語の概要は準備中です。原文の説明を表示しています。
Solves complex, open-ended problems using an evolutionary search mechanism inspired by genetic algorithms. Generates a diverse population of candidate answers, scores them against a rubric, then iteratively applies selection, crossover, and mutation to breed progressively better solutions. Use this skill whenever the user wants to explore a solution space deeply, asks for the "best" answer to a subjective or multi-dimensional problem, wants to evaluate competing approaches and distill the strongest, or uses any of these triggers: "evolutionary search", "genetic algorithm", "evolve an answer", "breed solutions", "population-based search", or phrases like "give me multiple approaches and refine the best one". Also trigger when the problem is complex, open-ended, or has no obvious single correct answer and the user wants a high-quality, well-explored result, not just a quick response.
日本語の概要は準備中です。原文の説明を表示しています。
Research and stress-test open-source project names, from collision checks to launch-ready decisions. Use when the user asks to name or rename a project, compare candidate names, screen GitHub or package namespace risk, verify language or mythology claims, or improve SEO/GEO clarity. Perform live web and registry research, separate brand from category descriptor, classify collisions, and return one evidence-backed recommendation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementation needs isolation from the current workspace; creates git worktrees with safe directory selection and baseline verification.
日本語の概要は準備中です。原文の説明を表示しています。
Add Emacs as a channel. Opens an interactive chat buffer and org-mode integration so you can talk to NanoClaw from within Emacs (Doom, Spacemacs, or vanilla). Uses a local HTTP bridge — no bot token or external service needed.
日本語の概要は準備中です。原文の説明を表示しています。
Quick read-only health check — session context, workspace mounts, tool availability, and task snapshot. Use when the user asks for system status or runs /status.
日本語の概要は準備中です。原文の説明を表示しています。
Add Emacs as a channel. Opens an interactive chat buffer and org-mode integration so you can talk to NanoClaw from within Emacs (Doom, Spacemacs, or vanilla). Uses a local HTTP bridge — no bot token or external service needed.
日本語の概要は準備中です。原文の説明を表示しています。
Quick read-only health check — session context, workspace mounts, tool availability, and task snapshot. Use when the user asks for system status or runs /status.
日本語の概要は準備中です。原文の説明を表示しています。
Find niches, topics, audiences, products, channels, and content angles via deep web search. Use whenever Ahmad says "find me a niche", "hunt niches in X", "what's an underserved audience for Y", "find similar sites/videos to <example>", "research the X market", "what are people building in Y space", "/niche-hunter X", or any phrasing that asks for niche / market / topic / audience / product / channel discovery across the open web. Trusts domain + keyword search; chains web_search → web_fetch / web_extract / web_crawl + reddit_search + search_youtube + github_repo_intel. NEVER uses awesome-list shortcuts. Output shape is FLEXIBLE — list, table, report, suggestions, or normal prose — picked from how Ahmad phrased the ask.
日本語の概要は準備中です。原文の説明を表示しています。
Manus-style file-based planning for multi-step work. Keep task_plan.md, findings.md, progress.md in your run workspace so the filesystem is your working memory. Use for any research/build with 5+ tool calls. Adapted for OpenMark sub-agents from Ahmad's planning-with-files v3.0.0.
日本語の概要は準備中です。原文の説明を表示しています。
Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Spectral vector search using graph Laplacian eigenstructure. Use when cosine/L2 similarity misses latent structure in your embeddings.
日本語の概要は準備中です。原文の説明を表示しています。
Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates.
日本語の概要は準備中です。原文の説明を表示しています。
Write and deploy Falco rules with the modern eBPF driver to detect container escape, namespace abuse, privileged mounts, and anomalous syscalls at runtime in Kubernetes and Docker.
日本語の概要は準備中です。原文の説明を表示しています。
Detect compromised O365 and Google Workspace email accounts by analyzing inbox rule creation, suspicious sign-in locations, mail forwarding rules, and unusual API access patterns via Microsoft Graph and audit logs.
日本語の概要は準備中です。原文の説明を表示しています。
Detect and prevent public-over-private name resolution in npm, PyPI, and Maven.
日本語の概要は準備中です。原文の説明を表示しています。
Detect and analyze heap spray attacks in memory dumps using Volatility3 plugins to identify NOP sled patterns, shellcode landing zones, and suspicious large allocations in process virtual address space.
日本語の概要は準備中です。原文の説明を表示しています。
Start a working doc — a drafting space where spec-level and implementation thinking co-exist before splitting into specs, plan, and test cases
日本語の概要は準備中です。原文の説明を表示しています。
Draft public Tamanu release notes for a given version. Use when the user wants release notes for a Tamanu release (e.g. "draft release notes for v2.45"). Pulls work from the specs and code that landed in that version's release/X.Y branch, plus the matching issues in the trackers (Linear's Tamanu team and Workhorse's Tamanu workspace), reconciles them, and writes docs/release-notes/vX-YY.md in the canonical v2.44 format for project managers and system administrators, plus a styled HTML rendering at .workhorse/design/designs/vX-YY-release-notes.html. Not for developer changelogs or QA test scoping (use scope-tamanu-release-tests for the latter).
日本語の概要は準備中です。原文の説明を表示しています。
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
日本語の概要は準備中です。原文の説明を表示しています。
Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn/run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Claude Code: use --print --permission-mode bypassPermissions (no PTY). Codex/Pi/OpenCode: pty:true required.
日本語の概要は準備中です。原文の説明を表示しています。
Use when managing Node.js dependencies with pnpm - provides workspace setup, catalogs, CLI commands, overrides, and CI configuration
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose and fix MARP slide layout issues including whitespace problems, box alignment, bullet formatting, and CSS rendering inconsistencies. Use when MARP slides have visual layout problems or need CSS optimization.
日本語の概要は準備中です。原文の説明を表示しています。