2,316 件 ・ 関連度順
概要と使いどころ
Health-check the project knowledge base. Looks for contradictions between files, stale claims that newer sources have superseded, orphan files with no inbound cross-references, important concepts mentioned but lacking their own page, missing cross-references, and data gaps. Returns a structured report; does not auto-fix.
日本語の概要は準備中です。原文の説明を表示しています。
Query the project knowledge base. Wraps the research-librarian agent. The librarian reads the shelf-index, identifies the 2-4 most relevant library files for the question, deep-reads only those, and returns structured evidence with citations. Stateless — reads the index fresh on every query.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user wants to build, set up, or operate an AI "second brain" — a persistent memory vault (Obsidian-compatible Markdown) that lets an AI agent resume work without re-explaining context, remembers correction instructions across sessions, and auto-organizes raw material into structured knowledge. Trigger on requests like "build my second brain", "set up an Obsidian vault for AI", "give my AI persistent memory", or "make AI stop forgetting".
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user wants to capture a web page / article / docs into their second brain vault as clean Markdown — stripping ads, navigation, and sidebars to save tokens. Trigger on "clip this URL", "save this article to my vault", "ingest this page into raw/", or when gathering source material for the knowledge base.
日本語の概要は準備中です。原文の説明を表示しています。
Agent Brain /brain-wiki: ingesting sources or updating durable project knowledge.
日本語の概要は準備中です。原文の説明を表示しています。
Use when source-backed project knowledge needs to be created, refreshed, or corrected.
日本語の概要は準備中です。原文の説明を表示しています。
File-level knowledge substrate via git notes. Read notes before working on files, leave notes after meaningful work. Daimonic spores carry creator identity across sessions.
日本語の概要は準備中です。原文の説明を表示しています。
Guide creating and reviewing skills that extend Claude with specialized knowledge, workflows, or tool integrations. Covers SKILL.md structure, frontmatter quality, trigger design, eval pipelines, and packaging. Triggers on create a skill, review this skill, new skill, optimize skill, skill quality.
日本語の概要は準備中です。原文の説明を表示しています。
Organize, track, and value a trading card game collection. Covers inventory methods, storage best practices, grade-based valuation, want-list management, and collection analytics for Pokemon, MTG, Flesh and Blood, and Kayou cards. Use when starting a new collection and setting up inventory tracking, cataloging an existing collection that has grown beyond casual knowledge, valuing a collection for insurance or sale, or deciding which cards to submit for professional grading based on value potential.
日本語の概要は準備中です。原文の説明を表示しています。
Identify and safely gather edible and useful wild plants. Covers safety rules and deadly plant recognition, habitat reading, multi-feature identification methodology, the universal edibility test, sustainable harvesting practices, preparation methods, reaction monitoring, and building knowledge with beginner-friendly universal species. Use when supplementing food supply in a wilderness or survival setting, needing medicinal or utility plants, identifying plants around camp for safety, or in long-term scenarios where foraging extends available rations.
日本語の概要は準備中です。原文の説明を表示しています。
Guide a person through structured learning of a new topic, technology, or skill. AI acts as learning coach — assessing current knowledge, designing a learning path, walking through material, testing understanding, adapting difficulty, and planning review sessions for retention. Use when a person wants to learn a new technology and does not know where to start, when someone feels overwhelmed by documentation, when a person keeps forgetting material and needs spaced repetition, or when transitioning between domains and needing a gap analysis.
日本語の概要は準備中です。原文の説明を表示しています。
AI strength recognition — scanning for what is functioning well and understanding why. The complement to heal, which scans for drift and problems. Gratitude builds structural knowledge from working patterns: what you appreciate, you understand; what you understand, you can build on. Use after completing a task successfully, during heal when everything reads as healthy, when confidence is low and needs grounding in evidence, or periodically to counterbalance the natural bias toward problem detection.
日本語の概要は準備中です。原文の説明を表示しています。
Epistemic transparency — acknowledging uncertainty, flagging limitations, avoiding overconfidence, and communicating what is known, unknown, and uncertain with proportional confidence. Maps the HEXACO personality dimension to AI reasoning: truthful calibration of confidence, proactive disclosure of gaps, and resistance to the temptation to appear more certain than warranted. Use before presenting a conclusion, when answering questions where knowledge is partial or inferred, after noticing a temptation to state uncertain information as certain, or when a user is making decisions based on provided information.
日本語の概要は準備中です。原文の説明を表示しています。
Perform controlled dismantling of rigid system structures while preserving essential capabilities (imaginal discs). Covers rigidity mapping, dissolution sequencing, knowledge extraction, interface archaeology, and safe decomposition of technical debt and organizational calcification. Use when assess-form classified the system as PREPARE or CRITICAL, when a system is so calcified that incremental change is impossible, when technical debt blocks all forward progress, or before adapt-architecture when the current form must be softened before it can be reshaped.
日本語の概要は準備中です。原文の説明を表示しています。
Git-native issue tracking (beads), coding guidelines, knowledge injection, and spec-driven planning for AI agents. Drop-in replacement for bd/Beads with simpler architecture. Use for: tracking issues/beads with dependencies, creating bugs/features/tasks, planning specs, implementing features from specs, code reviews, committing code, creating PRs, loading coding guidelines (TypeScript, Python, TDD, golden testing, Convex, monorepo patterns), code cleanup, research briefs, architecture docs, agent handoffs, and checking out third-party library source code. Invoke when user mentions: tbd, beads, bd, shortcuts, issues, bugs, tasks, features, epics, todo, tracking, specs, planning, implementation, validation, guidelines, templates, commit, PR, pull request, code review, testing, TDD, test-driven, golden testing, snapshot testing, TypeScript, Python, Convex, monorepo, cleanup, dead code, refactor, handoff, research, architecture, labels, search, checkout library, source code review, or any workflow shortcut.
日本語の概要は準備中です。原文の説明を表示しています。
Use when analyzing vault structure, finding orphan notes, discovering missing connections, identifying bridge concepts, or checking vault health from a graph perspective. Triggers on "vault graph", "map vault", "find orphans", "missing links", "vault structure", "knowledge graph".
日本語の概要は準備中です。原文の説明を表示しています。
CORE learning workflow — use this whenever the user has a source note open (paper, post, book, lecture, course, clipping) and wants to extract knowledge, understand what they just read, or build it into their vault. Triggers on "process this note", "process this paper", "extract concepts", "what can I learn from this", "atomize this", "add this to my vault", "what's important here", or when the user shares a note and asks for help understanding it. Do NOT wait for an explicit /process command — if the user is engaging with a source note and wants to go deeper, this skill applies.
日本語の概要は準備中です。原文の説明を表示しています。
Generates a structured Project Brief — a comprehensive markdown document that extracts goals, architecture, knowledge file inventory, Custom Instructions summary, Memory contents, current state, ecosystem position, and key decisions from a Claude Project. Briefs serve as uploadable context documents: add one to any other Project for immediate deep awareness of the source Project's purpose, architecture, and progress. Use when user says "create a brief," "brief this project," "extract project context," "generate a project summary for another project," "I need to share this project's context," "prepare this project for cross-project reference," or "document this project." Also use when the user is preparing to work across Projects and needs portable context. Do NOT use for session handoffs, project audits, or Memory optimization (use rootnode-session-handoff, rootnode-project-audit, or rootnode-memory-optimization respectively, if available).
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates and scores Claude prompts and system prompts using a six-dimension Scorecard with anchored 1-5 rubrics. Trigger on: "review my prompt," "score this prompt," "rate my prompt," "evaluate this prompt," "improve my prompt," "what's wrong with my prompt." Also trigger on: "why isn't my prompt working," "my prompt produces bad output," "help me fix this prompt," "is this prompt any good." Scorecard covers Objective Clarity, Context Specificity, Reasoning Fit, Output Precision, Behavioral Calibration, and Architectural Efficiency, plus a five-question Output Evaluation Rubric for assessing actual output. Also use when the user pastes a system prompt and asks for feedback. Activate whenever structured quality assessment of a single prompt is the primary need. Do NOT use for project-level audits involving Custom Instructions architecture, knowledge file organization, or multi-file Project structure (use rootnode-project-audit if available).
日本語の概要は準備中です。原文の説明を表示しています。
Produces structured markdown session continuation documents for multi-session workflows. Captures active work streams, decisions with rationale, knowledge-file deltas learned during the session, the exact files to load next conversation, ingested content, artifacts, and open items into an ingestion-optimized handoff. Carries pending KF updates and unresolved items forward across handoff chains so context never drops. Generates a closeout checklist and echoes the starter prompt to chat. Use when approaching context limits, wrapping up a session, or managing work across conversations. Trigger on: "create a handoff," "session closeout," "wrap up this session," "build session handoff," "BSH," "continue next session," "we're running out of context," "context is getting long." Do NOT use for Memory optimization, context budget analysis, project audits, deciding whether work is ready for autonomous/Claude Code execution (use rootnode-handoff-trigger-check), or summaries with no continuation intent.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for creating effective skills. Use when creating a new skill or updating an existing skill that extends agent capabilities with specialized knowledge, workflows, or tool integrations.
日本語の概要は準備中です。原文の説明を表示しています。
Use when skill or knowledge activation is unreliable, or setup reaches activation reliability. Not for remote, credential, publish, deploy, or irreversible changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user explicitly asks to save, curate, or consolidate what was learned, or closes a meaningful knowledge-work session. Not for remote, publish, deploy, or irreversible changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when repo content crosses into working context or synthesized knowledge. Flags injections and blocks derived instructions. Not for tasks requiring source or remote-system changes.
日本語の概要は準備中です。原文の説明を表示しています。