mark-evidence

Extract evidence identifiers from merged PRs and post manifest comments.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/ether-moon/knowledge-distillery --skill mark-evidence
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mark-evidence
Source: https://github.com/ether-moon/knowledge-distillery/tree/main/plugins/knowledge-distillery/skills/mark-evidence
Command: npx skills add https://github.com/ether-moon/knowledge-distillery --skill mark-evidence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically marks evidence identifiers in a PR when it is merged or invoked manually, producing a compact manifest that seeds Stage A of the distillation pipeline without fetching content.

Core Features & Use Cases

  • Evidence tagging at PR merge: extracts identifiers and posts an Evidence Bundle Manifest comment.
  • Stage A ready: lightweight, identifier-only data for downstream Stage B processing.
  • Idempotent & controllable: safe to re-run and compatible with the knowledge-distillery workflow.

Quick Start

Invoke mark-evidence on a merged PR or run /knowledge-distillery:mark-evidence <pr-number> to generate the manifest.

Frequently Asked Questions about mark-evidence

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

FAQPage Schema
How do I automatically extract evidence identifiers from a merged GitHub PR?▼

To automatically extract evidence identifiers from a merged GitHub PR, this Skill posts a lightweight Evidence Bundle Manifest comment containing identifier-only data without fetching content. It triggers upon PR merge or manual invocation with a PR number.

What is an Evidence Bundle Manifest in a knowledge distillation pipeline?▼

An Evidence Bundle Manifest is a compact, identifier-only data structure that seeds Stage A of the distillation pipeline. It marks evidence within a merged PR and passes structured data to Stage B for downstream processing.

Can I manually run evidence marking on a specific PR number?▼

Yes, you can manually run evidence marking on a specific PR by invoking the command with the desired PR number. This generates the manifest and safely updates the knowledge-pending label without requiring an actual merge event.

Is it safe to re-run PR evidence tagging multiple times on the same merge?▼

Yes, it is safe to re-run PR evidence tagging multiple times because the process strictly enforces idempotency. Re-running the action on an already marked PR safely duplicates the manifest generation without corrupting downstream Stage B processing.

Does the evidence manifest extraction fetch repository content or files?▼

No, evidence manifest extraction does not fetch repository content or files. It operates by solely extracting evidence identifiers from the PR to produce a lightweight manifest, ensuring fast execution without reading actual code changes.