mira-annotation

Annotate Markdown documents with MIRA research objects and source-local relations.

902|58|Updated May 31, 2012
One-click install
npx skills add https://github.com/stencila/stencila --skill mira-annotation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mira-annotation
Source: https://github.com/stencila/stencila/tree/main/.stencila/skills/mira-annotation
Command: npx skills add https://github.com/stencila/stencila --skill mira-annotation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scholarly Markdown documents often contain claims, evidence, questions, protocols, and requests that are not machine-readable, making it hard to trace which evidence supports which claim. This Skill adds semantic MIRA research-object annotations directly into the source Markdown without rewriting the author's wording.

Core Features & Use Cases

  • Research Object Annotation: Identifies and wraps claims, typed claims (hypothesis, theorem, proposition), evidence, questions, protocols, and requests using syntax idiomatic to the document's Markdown flavor.
  • Multi-Dialect Support: Detects and applies the correct syntax for Stencila Markdown (.smd), Quarto (.qmd), MyST (.myst), and plain Markdown (.md), preserving frontmatter, code cells, citations, and math.
  • Relation Encoding: Adds source-local relations such as supports, supported-by, opposes, addresses, and grounds as attributes pointing to unique kebab-case object ids.
  • Use Case: Given a Quarto manuscript with results and conclusions, annotate each conclusion as a claim linked via supported-by to the corresponding evidence block, producing a semantically structured document ready for Stencila publishing.

Quick Start

Annotate the attached manuscript.qmd with MIRA claims, evidence, and their supporting relations while preserving all Quarto syntax.

Frequently Asked Questions about mira-annotation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I annotate claims and evidence in Markdown documents?

Wrap claim and evidence passages in fenced blocks matching your Markdown flavor, such as ::: claim #claim-id for Stencila Markdown or ::: {.claim #id} for Quarto. Add relation attributes like supported-by pointing to the related object id.

What Markdown flavors support MIRA research object annotation?

MIRA annotation supports Stencila Markdown (.smd), Quarto (.qmd), MyST (.myst), and plain Markdown (.md). Each dialect uses its native syntax: colon fences for Stencila, fenced divs for Quarto, and directives for MyST.

Does MIRA annotation work with Quarto documents containing code cells?

Yes, Quarto annotation preserves YAML frontmatter, executable code chunks, chunk options, callouts, and cross-references. Annotations are added as fenced divs without moving or reformatting code cells.

When should I not use MIRA source annotation?

Avoid it for general copyediting, prose rewriting, or when you only want a separate knowledge graph without modifying the source. It is designed for semantic research-object annotation grounded in the document text.

How are relations between claims and evidence encoded?

Relations use attributes like supports, supported-by, opposes, addresses, and grounds, pointing to object ids with a leading # such as #evidence-study. Direction should match existing document conventions, and only explicit or strongly local relations are added.