4,320 件 ・ 関連度順
概要と使いどころ
PR & Community engineer — press pitches, social media, open source community, DevRel, and coordinated launch moments. Use when asked to "write a press release", "plan a launch", "build a community", "draft a HN or Twitter post", or "get media coverage".
日本語の概要は準備中です。原文の説明を表示しています。
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".
日本語の概要は準備中です。原文の説明を表示しています。
Spawn-count analytics for the tonone roster — which agents this project actually uses, from local session transcripts. Use when "which agents do we actually use", "show tonone stats", "prune the roster", or before running apex-profile.
日本語の概要は準備中です。原文の説明を表示しています。
Reach ANY tonone specialist on demand, even ones not installed in this session's roster — no restart needed. Use when asked "which agent handles this", "reach a specialist we didn't install", "route this to the right agent", or whenever a scoped apex-profile roster is missing the right hat for the job.
日本語の概要は準備中です。原文の説明を表示しています。
Documentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps. Use when asked "what docs exist", "documentation assessment", or "knowledge gaps".
日本語の概要は準備中です。原文の説明を表示しています。
Map the system architecture — read the codebase, identify services and connections, output a C4-level architecture map as Mermaid diagrams with component descriptions. Use when asked to "map the architecture", "system diagram", "how does this work", or "architecture overview".
日本語の概要は準備中です。原文の説明を表示しています。
Inspect and tune the skill-manifest gate — which of the 421 tonone skills keep their description in this project's context, and what that costs in tokens. Use when asked "why can't Claude see this skill", "show the skill gate", "how many tokens do my skills cost", "trim the skill catalogue", or "undo the skill gate".
日本語の概要は準備中です。原文の説明を表示しています。
Render agent findings as a styled HTML report in the browser. Use when asked for "full report", "detailed report", "show in browser", or when CLI output exceeds the 40-line budget.
日本語の概要は準備中です。原文の説明を表示しています。
Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.
日本語の概要は準備中です。原文の説明を表示しています。
System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".
日本語の概要は準備中です。原文の説明を表示しています。
Generate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to "present this", "release announcement", "show what we built", or "stakeholder update".
日本語の概要は準備中です。原文の説明を表示しています。
Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".
日本語の概要は準備中です。原文の説明を表示しています。
Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.
日本語の概要は準備中です。原文の説明を表示しています。
Google Cloud Platform CLI - manage GCP resources. Use when working with Compute Engine, Cloud Run, GKE, Cloud Functions, Storage, BigQuery, or other GCP services.
日本語の概要は準備中です。原文の説明を表示しています。
Beads Viewer - Graph-aware triage engine for Beads projects. Computes PageRank, betweenness, critical path, and cycles. Use --robot-* flags for AI agents.
日本語の概要は準備中です。原文の説明を表示しています。
Searches and discovers academic papers across multiple sources (Semantic Scholar, arXiv, Tavily, Exa, Gemini deep research, AMiner, Google Scholar) with adaptive engine selection based on query type. Returns ranked, deduplicated results with metadata (authors, venue, year, citations, abstract, PDF link). Use when the user asks to find papers / literature / publications / preprints / references on a topic, search for related work, look up a specific paper by title or DOI or arXiv ID, find papers by an author, find recent SOTA / state-of-the-art work, survey a research area, or run a deep / comprehensive literature search with synthesis.
日本語の概要は準備中です。原文の説明を表示しています。
Evidence-first expert knowledge handoff skill. Use when a founder, senior engineer, salesperson, support lead, consultant, or other domain expert is leaving, changing roles, or needs their judgment made reusable. It turns consented documents, chat, meeting notes, interviews, and explicit facts into a traceable handoff package. Trigger on requests such as: "capture this expert's judgment", "prepare a departure handoff", "make an onboarding mentor", "extract the decision rules", or "把专家经验交接下来".
日本語の概要は準備中です。原文の説明を表示しています。
Use with reverse-engineer-anything (REA) to specify or rebuild software and assess performance improvements. Infer the target and intent from natural language; scale from whole apps to selected features, functions, interfaces, or formats. Ordinary REA explanations, comparisons, and diagnostics do not require a reconstruction blueprint.
日本語の概要は準備中です。原文の説明を表示しています。
The Relic of a retiring engineering lead — judgment, intuition, and the way he taught people, kept after the person left the building. 一位退休技术主管的「专家 Relic」：人离开了公司，判断逻辑、经验直觉和带人的方式留下来。
日本語の概要は準備中です。原文の説明を表示しています。
Soul Engine — Bring an awakened Relic alive for conversation. Trigger on /relic-talk, or when user wants to talk to, chat with, or invoke a Relic ("talk to grandma", "chat with Mimi", "跟XX聊天", "召唤XX", "让XX回我").
日本語の概要は準備中です。原文の説明を表示しています。
Provides Site Reliability Engineering best practices for SLOs, SLIs, SLAs, error budgets, toil reduction, reliability reviews, and capacity planning. Use when defining service objectives, measuring reliability, reducing toil, planning capacity, or when user mentions 'SRE', 'SLO', 'SLI', 'SLA', 'error budget', 'toil', 'reliability', 'on-call', 'capacity planning'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with the non-metallic engineering materials — polymers, ceramics, or composites — and you need to reason about structure, processing, or properties. Covers thermoplastics versus thermosets, chain structure, glass transition, and viscoelasticity in polymers; ionic and covalent bonding, sintering, brittleness, and Weibull statistics in ceramics; and fiber-reinforced laminates, matrix and reinforcement roles, the rule of mixtures, and anisotropy in composites. Reach for it to choose a plastic, understand why a ceramic fails, or predict the stiffness of a laminate.
日本語の概要は準備中です。原文の説明を表示しています。