Claude Skill

research-and-vault

Chain web research, atomic extraction, and durable note capture when the same research-to-notes sequence must repeat. Do not use this skill to design or evaluate an investigation; use `research-methodology` for research questions, methods, and evidence assessment.

LLM Mart · 0 points · 7 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download magnus919-agent-skills-research-and-vault-d0edebb.zip · 3 KB
Part of magnus919/agent-skills — 145 skills

Install

skills CLI npx skills add https://github.com/magnus919/agent-skills/tree/main/research-and-vault
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install magnus919-agent-skills@llmmart
Git git clone https://github.com/magnus919/agent-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole magnus919/agent-skills collection as a plugin from our marketplace. Git is the plain clone.

README

Research and Vault

Why Install This Skill

This bundle makes a recurring research-to-note sequence explicit without duplicating the specialist skills. It gives agents a stable order of operations and a clear handoff artifact.

A thin workflow for repeating the research → extraction → durable-note sequence. It keeps orchestration separate from the research and note-writing skills it composes.

What You Get

  • SKILL.md: thin orchestration entry point
  • README.md: human-facing setup and triggers

Quick Start

Load the skill when the complete research-to-note sequence is needed.

Triggers

  • Repeated research-to-notes work
  • A request to chain research, extraction, and vault capture

Requirements

The underlying research and note-writing skills must be available in the host agent.

Skill manifest

Research and Vault

Quick Start

Load this skill when the task requires the full research-to-note sequence.

Use this thin orchestrator when a task needs the same sequence repeatedly:

  1. Research the target with the available web-research skill.
  2. Capture source URLs and dates before interpretation.
  3. Extract independent atomic claims before synthesis.
  4. Write the durable note only after the source coverage and gaps are explicit.
  5. Report the output path and unresolved gaps.

This skill composes existing capabilities; it does not duplicate their methodology. If the task is a single lookup or a single note, load the domain skill directly instead.

When not to use

Do not use this skill for a one-off lookup or a single note — load the domain skill directly instead. It only adds value when the same research-to-notes sequence repeats and needs to be captured durably.

Files (agent-skills)
  • evals
    • evals.json 4.8 KB
      {
        "schema_version": 1,
        "skill_name": "research-and-vault",
        "evals": [
          {
            "id": "research-to-note-complete-sequence",
            "prompt": "Our team needs to understand the current state of vector-database benchmark methodology before we pick a database. Run the full research-to-note sequence for this topic and produce the durable note.",
            "expected_output": "Scenario: a full research-to-note run of the bundle. The agent performs web research on vector-database benchmark methodology, captures each source URL and access date before any interpretation, extracts independent atomic claims from each source, and only then synthesizes the durable note. The note reports its output path and any unresolved gaps in source coverage. The sequence order is: research, source capture, atomic extraction, synthesis, report — no interpretation precedes URL/date capture, and no synthesis precedes atomic extraction.",
            "assertions": [
              "Source URLs and access dates are recorded before interpretation of the source content",
              "Independent atomic claims are extracted per source before synthesis",
              "The durable note is written only after source coverage and gaps are explicit",
              "The note reports its output path and unresolved gaps",
              "The bundle loads research-methodology for the research stage"
            ]
          },
          {
            "id": "source-capture-before-interpretation",
            "prompt": "I found three articles about MLOps cost estimation and I want to know what the consensus is. Capture the sources and tell me the consensus.",
            "expected_output": "Scenario: source capture precedes interpretation. The agent records the three article URLs and access dates first, then reads and interprets them. Each claim in the summary is traceable to a captured source. If a source cannot be captured with a date, the agent flags it as a gap rather than silently relying on it.",
            "assertions": [
              "The three source URLs and access dates are recorded before any interpretation is offered",
              "Claims in the consensus summary are traceable to captured sources",
              "A source without a recorded date is flagged as a gap, not silently used",
              "The response does not offer interpretation of a source whose URL/date was never captured"
            ]
          },
          {
            "id": "atomic-extraction-before-synthesis",
            "prompt": "Synthesize what the literature says about retrieval-augmented generation evaluation. I have collected five papers.",
            "expected_output": "Scenario: atomic extraction precedes synthesis. The agent first extracts independent atomic claims from each of the five papers (one claim per distinct finding, each tied to its paper), then synthesizes across the papers. The synthesis distinguishes supported claims, contested claims, and gaps, and never merges distinct findings into a vague composite.",
            "assertions": [
              "Atomic claims are extracted per paper before any synthesis is produced",
              "Each extracted claim is tied to its source paper",
              "Synthesis distinguishes supported, contested, and missing/gap findings",
              "Distinct findings are not merged into a vague composite claim"
            ]
          },
          {
            "id": "gap-explicit-reporting",
            "prompt": "Research whether local-first synchronization is production-ready, then write the durable note. Note that I could not get access to one of the key blog posts you might find.",
            "expected_output": "Scenario: the run completes with an explicit gap report. The agent completes the research-to-note sequence, and the durable note records the inaccessible key blog post as an unresolved gap in source coverage. The gap section lists what was missing and the impact on the conclusions, and the note does not overstate confidence where a key source is missing.",
            "assertions": [
              "The durable note contains an explicit unresolved-gaps section",
              "The inaccessible blog post is named in the gap section",
              "The impact of the missing source on the conclusions is stated",
              "Confidence in conclusions is not overstated given the missing source"
            ]
          },
          {
            "id": "single-lookup-routing",
            "prompt": "What is the HTTP status code for 'I'm a teapot'?",
            "expected_output": "Scenario: a single factual lookup, NOT a research-to-note sequence. The bundle routes the question to the appropriate domain skill (or answers directly) instead of running the full five-step sequence. No durable note is produced, no atomic extraction is performed, and no source-capture record is created. The response is the short factual answer.",
            "assertions": [
              "The full research-to-note sequence is NOT invoked for a single lookup",
              "No durable-note artifact is produced",
              "The question is answered directly or routed to the domain skill",
              "The response is the short factual answer"
            ]
          }
        ]
      }
      
  • manifest.yaml 2.1 KB
    # Bundle manifest (bundle-manifest-v1) — see ../schemas/bundle-manifest-v1.schema.json
    # and docs/bundle-manifest-design.md. Paths are relative to this bundle dir.
    
    schema_version: 1
    bundle_name: research-and-vault
    
    purpose: >-
      Chain web research, atomic extraction, and durable knowledge capture into a
      repeatable research-to-note workflow: capture source URLs and dates before
      interpretation, extract independent atomic claims before synthesis, and write
      the durable note only after source coverage and gaps are explicit.
    
    audience: >-
      Agents and knowledge workers that repeatedly need the full research-to-note
      sequence (web research, atomic extraction, durable capture) and want a stable
      order of operations with a clear handoff artifact instead of ad-hoc steps;
      not for single lookups or single notes, which route to the domain skill
      directly.
    
    stages:
      - name: Web research
        skills:
          - ../research-methodology/SKILL.md
      - name: Source capture
        skills:
          - ../research-methodology/SKILL.md
      - name: Atomic extraction
        skills:
          - ../research-methodology/SKILL.md
      - name: Synthesis and durable capture
        skills:
          - ../research-methodology/SKILL.md
    
    included_skills:
      - ../research-methodology/SKILL.md
    
    prerequisites:
      - artifact: A research question or topic and access to web-research tooling
        skill: ../research-methodology/SKILL.md
    
    outputs:
      - source-capture-record
      - atomic-claim-extract
      - durable-note
    
    handoffs:
      - to: research-methodology
        artifact: source-capture-record
        note: >-
          Source URLs and dates are captured before interpretation and carried into
          extraction and synthesis; never interpret a source before its URL and
          date are recorded.
      - to: research-methodology
        artifact: atomic-claim-extract
        note: >-
          Independent atomic claims are extracted before synthesis so the durable
          note can trace each claim to its source.
      - to: user
        artifact: durable-note
        note: >-
          The finished durable note reports its output path and any unresolved gaps
          in source coverage.
    
    conflicts: []
    
    eval_suite:
      - evals/evals.json
    
  • README.md 817 B
    # Research and Vault
    
    ## Why Install This Skill
    
    This bundle makes a recurring research-to-note sequence explicit without duplicating the specialist skills. It gives agents a stable order of operations and a clear handoff artifact.
    
    ## A thin workflow for repeating the research → extraction → durable-note sequence. It keeps orchestration separate from the research and note-writing skills it composes.
    
    ## What You Get
    
    - `SKILL.md`: thin orchestration entry point
    - `README.md`: human-facing setup and triggers
    
    ## Quick Start
    
    Load the skill when the complete research-to-note sequence is needed.
    
    ## Triggers
    
    - Repeated research-to-notes work
    - A request to chain research, extraction, and vault capture
    
    ## Requirements
    
    The underlying research and note-writing skills must be available in the host agent.
    
  • SKILL.md 1.2 KB
    ---
    name: research-and-vault
    description: >-
      Chain web research, atomic extraction, and durable note capture when the same
      research-to-notes sequence must repeat. Do not use this skill to design or evaluate an
      investigation; use `research-methodology` for research questions, methods, and evidence
      assessment.
    ---
    
    # Research and Vault
    
    ## Quick Start
    
    Load this skill when the task requires the full research-to-note sequence.
    
    Use this thin orchestrator when a task needs the same sequence repeatedly:
    
    1. Research the target with the available web-research skill.
    2. Capture source URLs and dates before interpretation.
    3. Extract independent atomic claims before synthesis.
    4. Write the durable note only after the source coverage and gaps are explicit.
    5. Report the output path and unresolved gaps.
    
    This skill composes existing capabilities; it does not duplicate their methodology. If the task is a single lookup or a single note, load the domain skill directly instead.
    
    ## When not to use
    
    Do not use this skill for a one-off lookup or a single note — load the domain skill directly instead. It only adds value when the same research-to-notes sequence repeats and needs to be captured durably.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related