Claude Cursor Skill

research-artifacts

Organize, format, and index research as OKF-conformant knowledge bundles — dated, sourced, append-only snapshots of the external evidence behind a decision (technology evaluations, library comparisons, industry-practice surveys). Use when recording research output, structuring a

LLM Mart · 0 points · 4 views 0 listing impressions 0 install-command copies

#research

Download ejklock-living-docs-skill-skills_research-artifacts-2d29395.zip · 7 KB

Install

skills CLI npx skills add https://github.com/ejklock/living-docs-skill/tree/main/skills/research-artifacts
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install ejklock-living-docs-skill@llmmart
Git git clone https://github.com/ejklock/living-docs-skill.git

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

Skill manifest

Research Artifacts

Research records the external evidence behind a decision: technology evaluations, library comparisons, industry-practice surveys. Research is dated, sourced, and append-only — a snapshot of what the evidence said at a point in time, not a living opinion.

This skill defines how research is organized, formatted, and indexed. The deep-research skill defines how it is gathered and cross-verified; living-docs owns the decisions and issues it feeds. The three compose. Research artifacts are OKF concepts — see the okf-knowledge-format skill for the frontmatter/reserved-file rules applied here.


Using this skill (progressive disclosure)

This SKILL.md is a slim stub — a trigger plus a task->topic router. The living-docs CLI holds the full research rules, source discipline, structure and traceable chain, and discloses them progressively. Before authoring anything, load the topic for your task:

  • living-docs read guide --list — discover every topic.
  • living-docs read guide <topic> --skill research-artifacts — load that topic.

Piped output is minified JSON (machine default); --plain for human text, --json to force JSON. Topics: rules, structure, research-report, research-index, research-general-references, about.

This stub is a pure router (ADR 0017): it triggers and points at topics — it holds no rules inline. The source discipline and the research → decision → issue chain are topics, loaded before authoring via read guide rules --skill research-artifacts / read guide structure --skill research-artifacts.


When to invoke

  • Recording the output of a research session into docs/research/ — living-docs read guide research-report --skill research-artifacts.
  • Structuring or indexing a research note (docs/research/NNNN-<slug>.md + the index listing + the general roll-up) — living-docs read guide research-index --skill research-artifacts / read guide research-general-references --skill research-artifacts for the templates, read guide structure --skill research-artifacts for the layout rules.
  • Enforcing source discipline on a draft (primary sources, vendor-COI flags, inference-vs-fact labels, confidence levels, fetch-failure notes) — living-docs read guide rules --skill research-artifacts.
  • Wiring the research → decision → issue traceable chain (an accepted recommendation must reach an ADR and then issues, in living-docs) — living-docs read guide structure --skill research-artifacts.
Files (living-docs-skill)
  • rules
    • about.md 366 B
      Loading…
    • rules.md 4.3 KB
      Loading…
    • structure.md 3.3 KB
      Loading…
  • templates
    • research-general-references.md 1.2 KB
      Loading…
    • research-index.md 494 B
      Loading…
    • research-report.md 1.7 KB
      Loading…
  • SKILL.md 3.3 KB
    ---
    name: research-artifacts
    description: Organize, format, and index research as OKF-conformant knowledge bundles — dated, sourced, append-only snapshots of the external evidence behind a decision (technology evaluations, library comparisons, industry-practice surveys). Use when recording research output, structuring a docs/research/ session, enforcing source discipline (primary sources, vendor-COI flags, inference-vs-fact labels, confidence levels), or wiring the research → decision → issue traceable chain. Pairs with deep-research (which gathers/verifies the evidence) and living-docs (which owns the ADR/issue artifacts research feeds into).
    version: "0.30.0"
    metadata:
      type: skill
      layer: procedural
      tags: [documentation, research, evidence, okf, sourcing, traceability]
    ---
    
    # Research Artifacts
    
    Research records the external evidence behind a decision: technology evaluations, library comparisons, industry-practice surveys. Research is **dated, sourced, and append-only** — a snapshot of what the evidence said at a point in time, not a living opinion.
    
    This skill defines how research is *organized, formatted, and indexed*. The `deep-research` skill defines how it is *gathered and cross-verified*; `living-docs` owns the decisions and issues it feeds. The three compose. Research artifacts are **OKF concepts** — see the `okf-knowledge-format` skill for the frontmatter/reserved-file rules applied here.
    
    ---
    
    ## Using this skill (progressive disclosure)
    
    This SKILL.md is a **slim stub** — a trigger plus a task->topic router. The `living-docs` CLI holds the full research rules, source discipline, structure and traceable chain, and discloses them progressively. **Before authoring anything, load the topic for your task:**
    
    - `living-docs read guide --list` — discover every topic.
    - `living-docs read guide <topic> --skill research-artifacts` — load that topic.
    
    Piped output is minified JSON (machine default); `--plain` for human text, `--json` to force JSON. Topics: rules, structure, research-report, research-index, research-general-references, about.
    
    This stub is a **pure router** (ADR 0017): it triggers and points at topics — it holds no rules inline. The source discipline and the research → decision → issue chain are topics, loaded before authoring via `read guide rules --skill research-artifacts` / `read guide structure --skill research-artifacts`.
    
    ---
    
    ## When to invoke
    
    - Recording the output of a research session into `docs/research/` — `living-docs read guide research-report --skill research-artifacts`.
    - Structuring or indexing a research note (`docs/research/NNNN-<slug>.md` + the index listing + the general roll-up) — `living-docs read guide research-index --skill research-artifacts` / `read guide research-general-references --skill research-artifacts` for the templates, `read guide structure --skill research-artifacts` for the layout rules.
    - Enforcing source discipline on a draft (primary sources, vendor-COI flags, inference-vs-fact labels, confidence levels, fetch-failure notes) — `living-docs read guide rules --skill research-artifacts`.
    - Wiring the research → decision → issue traceable chain (an accepted recommendation must reach an ADR and then issues, in `living-docs`) — `living-docs read guide structure --skill research-artifacts`.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.