AGENT SKILL

research-and-incorporate

Research external topics, create comprehensive analysis, determine project applicability, and incorporate learnings into Brain memory notes. Transforms knowledge into searchable, actionable project context.

License 许可
MIT
所属仓库
loriensleafs/brain
最近更新
2026-03-11
Stars
★ 0
Forks
0

01 前言 Front Matter

name
research-and-incorporate
model
claude-opus-4-5
agents
[ "analyst", "memory" ]
license
MIT
metadata
{ "version": "2.0.0", "timelessness": "8/10" }
description
Research external topics, create comprehensive analysis, determine project applicability, and incorporate learnings into Brain memory notes. Transforms knowledge into searchable, actionable project context.

02 资源文件 104

03 SKILL.md 正文

Research and Incorporate

Transform external knowledge into actionable, searchable project context through structured research, analysis, and memory integration.

Quick Start

/research-and-incorporate

Topic: Chesterton's Fence
Context: Decision-making principle for understanding existing systems before changing them
URLs: https://fs.blog/chestertons-fence/, https://en.wikipedia.org/wiki/G._K._Chesterton
Input Output Duration
Topic + Context + URLs Analysis note + Brain memory notes 20-40 min

Triggers

  • /research-and-incorporate - Main invocation
  • research and incorporate {topic} - Natural language
  • study {topic} and add to memory - Alternative phrasing
  • deep dive on {topic} - Research focus
  • learn about {topic} for the project - Project integration focus

When to Use

Use this skill when:

  • Researching an external concept, framework, or principle for project integration
  • You need structured analysis with memory persistence (not just a web search)
  • Building actionable knowledge from external sources

Use memory-documentary instead when:

  • Investigating patterns already in existing memory systems
  • You need cross-system evidence synthesis, not new external research

Parameters

Parameter Required Description
TOPIC Yes Subject to research (e.g., "Chesterton's Fence")
CONTEXT Yes Why this matters to the project
URLS No Comma-separated source URLs

Process

Phase 1: RESEARCH (BLOCKING)
  - Check existing knowledge (Brain MCP search)
  - Fetch URLs with quote extraction
  - Web search for additional context
  - Synthesize: principles, frameworks, examples, failure modes

Phase 2: ANALYSIS DOCUMENT (BLOCKING)
  - Write 3000-5000 word analysis as Brain memory note in analysis/
  - Include: concepts, frameworks, applications, failure modes
  - Verify: 3+ examples, 3+ failure modes, 2+ relationships

Phase 3: APPLICABILITY (BLOCKING)
  - Map integration points: agents, protocols, memory, skills
  - Propose applications with effort estimates
  - Prioritize: High/Medium/Low based on project goals

Phase 4: MEMORY INTEGRATION (BLOCKING)
  - Create Brain memory notes for key atomic concepts
  - Add relations via wikilinks to connect knowledge
  - Each note: one concept, proper entity type, observations, relations

Phase 5: ACTION ITEMS
  - Create GitHub issue if implementation work identified
  - Document in session log

Quality Gates (BLOCKING)

Gate Requirement Phase
Research depth Core principles + frameworks + 3 examples 1
Analysis length 3000-5000 words minimum 2
Concrete examples 3+ with context and outcomes 2
Failure modes 3+ anti-patterns with corrections 2
Relationships 2+ connections to existing concepts 2
Note quality Each note has 3+ observations, 2+ relations 4
Note count 5-10 Brain memory notes created 4

Verification Checklist

After completion, verify:

  • [ ] Analysis note exists in Brain memory analysis/ folder
  • [ ] Analysis is 3000-5000 words with concrete examples
  • [ ] Applicability section documents integration opportunities
  • [ ] 5-10 Brain memory notes created with proper entity types
  • [ ] Notes have observations (3+) and relations (2+)
  • [ ] Notes linked to related concepts via wikilinks
  • [ ] Each note is atomic (one concept per note)
  • [ ] Action items documented (issue or next steps)

Anti-Patterns

Avoid Why Instead
Superficial research Surface definitions miss actionable insights Dig into frameworks, examples, failure modes
Missing applicability Research without integration is wasted Every insight must show HOW it applies
Notes without observations Missing categorized facts makes notes hard to query Add 3+ observations with categories and tags
Disconnected knowledge Orphaned notes are not discoverable Add relations via wikilinks to connect knowledge
Template over-compliance Forcing irrelevant sections wastes tokens Organize for the topic, not the template
Skipping verification Quality gates exist for a reason Verify each phase before proceeding

Related Skills

Skill Relationship
exploring-knowledge-graph Navigate created knowledge
curating-memories Update and maintain created notes
memory Search and retrieve incorporated knowledge

References

Document Content
workflow.md Detailed phase workflows with templates
memory-templates.md Brain memory note structure templates

Extension Points

  1. Additional research sources: Add MCP tools for specialized domains
  2. Custom analysis templates: Topic-specific document structures
  3. Automated validation: Scripts to verify note quality
  4. Integration hooks: Connect to ADR review for architecture topics

04 同仓库更多 Skills

loriensleafs
loriensleafs/brain

validation-authority

Treat upstream validators as authoritative. Align local config to them. Use when validation fails unexpectedly, before modifying validator behavior, or when tempted to change upstream tool code.

★ 0
loriensleafs
loriensleafs/brain

using-brain-memory

Guidance for using Brain semantic memory effectively. Applies Zettelkasten atomic note principles with observations and relations. Use when deciding whether to query or create notes, structuring note content, or understanding the semantic knowledge graph.

★ 0
loriensleafs
loriensleafs/brain

threat-modeling

Structured security analysis using OWASP Four-Question Framework and STRIDE methodology. Generates threat matrices with risk ratings, mitigations, and prioritization. Use for attack surface analysis, security architecture review, or when asking what can go wrong.

★ 0
loriensleafs
loriensleafs/brain

taste-lints

Custom lints with agent-readable remediation instructions. Enforces taste invariants (file size, naming conventions, structured logging, complexity) and surfaces errors that agents can act on directly. Use when writing or reviewing code to catch style violations early.

Skill与智能体开发
★ 0
loriensleafs
loriensleafs/brain

style-enforcement

Validate code against style rules from .editorconfig, StyleCop.json, and Directory.Build.props. Detects line ending violations, naming convention issues, indentation problems, and charset mismatches across C#, Python, TypeScript, and JavaScript. Produces JSON reports for pre-commit hooks and CI pipelines.

★ 0
loriensleafs
loriensleafs/brain

steering-matcher

Match file paths against steering file glob patterns to determine applicable steering guidance. Use when orchestrator needs to inject context-aware guidance based on files being modified.

★ 0