plugins/context-ledger/skills/collecting-evidence/SKILL.md
Use when researching a specific pillar and need to create traceable evidence objects. Guides creation of YAML evidence files with semantic IDs, confidence scores, and assumptions.
npx skillsauth add synaptiai/synapti-marketplace collecting-evidenceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill guides the creation of structured Evidence Objects for a single research pillar.
/ledger-init completed)01-pillars/PILLARS.mdUse TodoWrite to track these mandatory steps:
<required> 1. Load pillar scope and research questions 2. Identify evidence sources 3. Collect raw evidence 4. Create Evidence Objects with semantic IDs 5. Validate evidence quality 6. Check evidence gate (minimum 5 per pillar) </required>Read 01-pillars/PILLARS.md to understand:
See references/research-protocols.md for pillar-specific protocols.
For each research question, identify potential sources:
| Source Type | Examples | Typical Confidence |
|-------------|----------|-------------------|
| url | Research reports, documentation | 60-90 |
| pdf | Academic papers, whitepapers | 70-95 |
| interview | User interviews, expert calls | 50-80 |
| internal-doc | Company data, prior research | 60-85 |
| experiment | A/B tests, prototypes | 70-95 |
| dataset | Analytics, survey results | 65-90 |
For each source:
Web research protocol:
Write YAML files to 02-evidence/<pillar>/.
Naming: Use semantic IDs per references/id-generation-rules.md.
Schema: See references/evidence-object-schema.md.
<good-example> ```yaml id: EV-market-pricing-smb-wtp pillar: market source: type: url ref: "https://example.com/pricing-research" retrieved_at: 2026-01-21 claim: "SMB segment willingness-to-pay peaks at $29/mo for productivity tools." quote: "Our survey of 500 SMBs found median WTP of $29/month..." confidence: 0.75 assumptions: - "Survey sample representative of target market" - "WTP for 'productivity tools' applies to our specific category" notes: "Sample skewed toward US companies. May need regional validation." tags: - pricing - smb - wtp ``` - Semantic ID describes content (market-pricing-smb-wtp) - Falsifiable claim with specific number ($29/mo) - Honest confidence (0.75, not inflated) - Explicit assumptions documented - Source fully traceable </good-example> <bad-example> ```yaml id: EV-001 pillar: market source: type: url ref: "some website" claim: "People like our product" confidence: 0.95 assumptions: [] ``` - Non-semantic ID (EV-001 tells nothing about content) - Vague, unfalsifiable claim ("people like") - Overconfident (0.95) without strong source - No assumptions documented - Untraceable source reference </bad-example>Each Evidence Object must pass:
| Check | Requirement | |-------|-------------| | Falsifiable claim | Claim can be proven wrong | | Confidence assigned | 0.0-1.0 value present | | Assumptions listed | At least 1 assumption | | Source traceable | Can revisit the source | | ID is semantic | Follows ID scheme |
Quality warnings:
Before synthesis, verify minimum 5 Evidence Objects per pillar.
Evidence Gate Check: market
├── EV-market-tam-b2b-saas ✓
├── EV-market-pricing-smb-wtp ✓
├── EV-market-growth-remote-tools ✓
├── EV-market-segment-priorities ✓
└── EV-market-competitive-density ✓
Total: 5/5 minimum ✓ GATE PASSED
If gate fails, continue research until threshold met.
Use the AskUserQuestion tool when:
Question: "Multiple sources available for [topic]. Which to prioritize?"
Options:
- "Academic/peer-reviewed sources (higher confidence)"
- "Recent industry reports (more current)"
- "Direct user research (more specific)"
- "Research all and compare"
Question: "How confident should I rate this claim: '[claim]'?"
Options:
- "High (0.8-0.9) - Strong source, well-supported"
- "Medium (0.5-0.7) - Reasonable source, some uncertainty"
- "Low (0.3-0.5) - Weak source or significant assumptions"
- "Help me assess the source quality"
Question: "Sources disagree on [topic]. Source A says X, Source B says Y."
Options:
- "Create evidence for both, note contradiction"
- "Prioritize more recent source"
- "Prioritize more authoritative source"
- "Research further for resolution"
Question: "Only [N] evidence objects for [pillar]. Need [5-N] more to pass gate."
Options:
- "Continue researching this pillar"
- "Accept partial evidence (will affect synthesis quality)"
- "Deprioritize this pillar for MVP"
- "Help me identify additional research areas"
After evidence collection:
## Evidence Collection Complete: [pillar]
**Evidence Objects Created:** [N]
**Gate Status:** [PASSED/FAILED]
### Evidence Summary
| ID | Claim Summary | Confidence |
|----|---------------|------------|
| EV-market-tam-b2b-saas | TAM is $X billion | 0.80 |
| EV-market-pricing-smb-wtp | SMB WTP peaks at $29/mo | 0.75 |
| ... | ... | ... |
### Key Findings
- [Top 3 findings from this pillar]
### Contradictions Noted
- [Any conflicting evidence]
### Gaps Remaining
- [Research questions not fully answered]
tools
Validate a FlowWorkflow YAML at `plugins/flow/workflows/<id>.workflow.yaml` against `schemas/v1/workflow.schema.json` AND cross-reference the referenced skills/agents exist + every Tier 3 action is confirm-gated + no native /goal or /loop dependency is declared. Use when /flow:workflow validate is invoked, when CI runs the workflow schema gates, or when a new workflow is being authored. This skill MUST be consulted because schema validation alone catches shape errors; cross-reference validation catches the silent-correctness failures (typo'd skill name, Tier 3 escape, /goal dependency) that would otherwise ship to users.
tools
Verify UI-facing changes by running a screenshot-analyze-verify loop across configured viewports, with a browser-tool priority cascade (Playwright MCP → Chrome DevTools MCP → CLI fallback → external skill fallback) and bounded iteration. Use after build/runtime verification passes and the diff includes `.tsx`/`.jsx`/`.vue`/`.html`/`.css`/`.scss`/`.svelte` files OR the acceptance criteria mention UI/page/render/display/visual. This skill MUST be consulted because UI changes that pass build and unit tests can still ship blank pages, render-blocking console errors, or broken responsive layouts that no other verification phase catches.
data-ai
Coordinate agent teams for adversarial review (paired skeptic/verifier per facet, challenge round with disposition vocabulary, consolidated findings with confidence) or parallel implementation (task sizing 5-6 per teammate, non-overlapping files). Enforces independent analysis before shared conclusions. Reference only (`disable-model-invocation: true`); loaded only when `agentTeams: true` in settings.
development
Conduct two-stage code review: Stage 1 verifies spec compliance (criterion-to-code mapping), Stage 2 evaluates security, correctness, performance, and maintainability across 6 parallel facets with P1/P2/P3 synthesis and deduplication by file:line. Use when reviewing code changes or pull requests. This skill MUST be consulted because reviewing quality on broken logic is wasted effort, and unmet acceptance criteria must block merge.