Control Knowledge Explorer

Control Knowledge Explorer

When to use

Use this skill at the start of a research topic or when evidence is fragmented across KB, logs, and papers.

Knowledge And Tool Interaction

1. Use eda-context-accessor when the task first needs a shared scoped KB/tool snapshot before deeper evidence-gap mapping begins.
2. Treat the local knowledge base as the primary evidence source once exploration starts.
3. Write outputs as reusable knowledge artifacts that later skills can consume directly.

Workflow

1. Read core KB context and recent experiment summaries.
2. Build a gap map:

• known claims,
• uncertain assumptions,
• missing evidence.

1. For missing external evidence, delegate to eda-paper-fetch and generate a local download queue.
2. If local PDFs are available, delegate parse/summarize to eda-pdf-local-summary.
3. Produce explicit research questions that can be tested in later experiment design.

Outputs

1. knowledge_gap_map.md
2. paper_download_queue.tsv
3. evidence_to_question_map.md

Hard rules

1. Distinguish confirmed evidence from hypotheses.
2. Do not present unsourced claims as conclusions.
3. Keep file/path-level references for each key claim.

Reference

Load when needed:

1. references/exploration-checklist.md

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: Mr-Fang-VLSI
• Source: Mr-Fang-VLSI/EDAgent
• License: MIT

Install and usage instructions live in the source repository linked above.