ln-311-review-research-worker
Use when an evaluation run needs mandatory official-doc, MCP Ref, Context7, and current best-practice research with a structured research summary.
What this skill does
> **Paths:** File paths (`references/`, `../ln-*`) are relative to this skill directory. **Type:** L3 Worker **Category:** 3XX Planning # Review Research Worker Structured research worker for validation, audit, and review flows. ## Mandatory Read **MANDATORY READ:** Load `references/evaluation_worker_runtime_contract.md`, `references/evaluation_summary_contract.md`, `references/evaluation_research_contract.md`, `references/epistemic_protocol.md` **MANDATORY READ:** Load `references/researchgraph_mcp_usage.md` only when the review target explicitly cites `H##`, `G##`, benchmark run IDs, or researchgraph files. ## Purpose - gather official documentation or standards - gather MCP Ref evidence - gather Context7 evidence when a library or framework is involved - gather current web best-practice evidence - emit a compact machine-readable research summary instead of prose-only notes ## Runtime Runtime family: - `evaluation-worker-runtime` Required manifest fields: - `identifier` - `phase_order` - `summary_kind=review-research` - `operation=research` Recommended `phase_order`: 1. `PHASE_0_CONFIG` 2. `PHASE_1_RESOLVE_STACK` 3. `PHASE_2_OFFICIAL_DOCS` 4. `PHASE_3_MCP_REF` 5. `PHASE_4_CONTEXT7` 6. `PHASE_5_WEB_BEST_PRACTICES` 7. `PHASE_6_ANTI_HALLUCINATION` 8. `PHASE_7_WRITE_SUMMARY` 9. `PHASE_8_SELF_CHECK` ## Workflow ### Phase 0: Config 1. Load runtime manifest. 2. Resolve review target, stack hints, and output location. 3. Fail if target context is missing. ### Phase 1: Resolve Stack 1. Detect language, framework, libraries, and domain. 2. Build a bounded research topic list. 3. Keep topic count small and evidence-oriented. 4. If the target explicitly cites local H/G/run IDs, do a read-only researchgraph preflight to capture local context before external research. Do not replace official-doc, MCP Ref, Context7, or current-web lanes with local graph evidence. ### Phase 2: Official Docs 1. Read official docs or standards first. 2. Record source URLs and the exact topic each source supports. ### Phase 3: MCP Ref 1. Query MCP Ref for the same bounded topics. 2. Prefer primary documentation over tertiary commentary. ### Phase 4: Context7 1. If a library or framework is involved, resolve the Context7 library id. 2. Query only the libraries actually used by the target. 3. If no relevant library exists, record that explicitly. ### Phase 5: Web Best Practices 1. Perform current web research for best practices and recent changes. 2. Use current sources, not frozen heuristics. 3. Record only evidence that changes a conclusion or adds decision value. ### Phase 6: Anti-Hallucination Verification 1. Scan target artifact for factual claims across all trigger categories per `epistemic_protocol.md` Section B. 2. For each claim, check against research evidence gathered in Phases 2-5: - Has MCP Ref/Context7/Web evidence → mark `VERIFIED` - No tool evidence but claim is plausible → mark `FROM_TRAINING` - Contradicts tool evidence → mark `FLAGGED` (CRITICAL) 3. This step verifies against existing research. It does NOT run new searches. 4. Include verification status in summary metadata. ### Phase 7: Write Summary Emit `summary_kind=review-research`. Payload must include: - `worker=ln-311` - `status` - `operation=research` - `warnings` Prefer these fields when available: - `findings` - `metrics.research_sources` - `metrics.anti_hallucination_status` (VERIFIED | FLAGGED) - `metrics.flagged_claims_count` - `artifact_path` - `report_path` - `metadata` ### Phase 8: Self-Check 1. Verify all four research lanes were attempted. 2. Verify anti-hallucination verification was executed. 3. Verify skipped lanes are justified in machine-readable form. 4. Record `pass=true` only after the summary is written. ## Definition of Done - [ ] Official-doc evidence recorded - [ ] MCP Ref evidence recorded - [ ] Context7 evidence recorded or justified as not applicable - [ ] Current web best-practice evidence recorded - [ ] Anti-hallucination verification executed (claims marked VERIFIED/FROM_TRAINING/FLAGGED) - [ ] `review-research` summary written - [ ] Self-check passed **Version:** 1.0.0 **Last Updated:** 2026-04-10
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.