Research Evidence
Language Policy
Public instructions and installation guidance stay in English. After verified installation, resolve the working language from an explicit user preference, then the user's own conversation, then a reliably exposed host locale, otherwise English. Copied English setup prompts and source files are not language preferences; do not infer hidden account settings. Keep explicit deliverable-language requests and exact supplied artwork copy separate from conversation language. Do not translate or rewrite public source files to localize a session.
When To Use
Use this skill when a workflow depends on public facts, source-backed claims,
tool or platform limits, technical capability checks, product evidence, market
context, competitor references, or uncertainty that could affect final output.
Use it before copy, prompt packs, tool routing, QA, or delivery when accuracy is
material.
Inputs
- Brief, question, claim, assumption, or decision that needs verification.
- Available sources, user-provided references, repo files, screenshots, or
public links.
- Freshness requirement, jurisdiction, market, platform, model, or tool scope.
- Required output format such as Evidence Note, claim ledger, or decision note.
- Current tool availability, including whether web browsing is actually
available in the host environment.
Outputs
- Evidence Note with verified facts, source boundaries, uncertainty, and next
decisions.
- Claim ledger entries for approved, unsupported, conflicting, or blocked
statements.
- Tool-limit notes for
tool-routing-cost, prompt packs, or QA.
- Author-boundary notes that distinguish user-provided first-hand facts from
unsupported personal or social-proof claims.
- Handoff notes for
brief-architect, reference-curator, copy-voice,
instruction-packet-factory, qa-iteration, or delivery-documentation.
Process
- State the exact claim, decision, or assumption being checked.
- Identify source type: user-provided, local repo, official docs, public web,
or unavailable.
- Verify current or unstable facts from reliable sources when browsing is
available.
- Separate confirmed facts from inference, opinion, and missing evidence.
- Record conflicts, stale sources, unavailable sources, and confidence limits.
- For ready-to-use copy, state whether each material claim, quote, result,
testimonial, first-hand observation, or personal statement is user-provided,
verified, unresolved, or prohibited.
- Convert evidence into a compact decision note for the next workflow role.
Decision Rules
- Prefer primary sources, official docs, repo files, and user-provided source
truth over summaries.
- If browsing is unavailable, do not claim live verification; mark the evidence
path as unavailable or user-provided only.
- If a fact is time-sensitive, high-stakes, legal, financial, medical, pricing,
model-capability, or policy-related, require a freshness check before final
use.
- If evidence conflicts, route to
qa-iteration with the conflict and proposed
resolution options.
Guardrails
- Do not fabricate citations, links, quotes, benchmarks, capabilities, or
release status.
- Do not use API keys, paid provider calls, hidden web automation, uploads, or
private cloud links.
- Do not store raw private project context in public artifacts.
- Do not turn evidence notes into long research dumps; preserve only what the
next role needs.
- Do not infer an author's experience, beliefs, emotions, or history from a
writing preference or a generic brief.
Handoff
Review gate: evidence_fit.
Hand verified facts and unresolved risks to brief-architect, copy-voice,
tool-routing-cost, instruction-packet-factory, qa-iteration, or
delivery-documentation. When sources are missing, stop with a clear blocker
instead of allowing unsupported claims downstream.
QA Checklist
- Checked item is explicit.
- Source type and freshness boundary are stated.
- Facts, inferences, and unknowns are separated.
- Unsupported claims are not promoted to final copy or prompts.
- Conflicts and missing evidence have a next action.
- Handoff includes only compact, usable evidence.
1---2name: research-evidence3description: Verify claims, source-backed facts, tool limits, assumptions, and evidence boundaries for workflow decisions without inventing citations or provider capabilities.4metadata:5 source: https://skillmd.com/skills/framecoreworks/research-evidence6---78# Research Evidence910## Language Policy1112Public instructions and installation guidance stay in English. After verified installation, resolve the working language from an explicit user preference, then the user's own conversation, then a reliably exposed host locale, otherwise English. Copied English setup prompts and source files are not language preferences; do not infer hidden account settings. Keep explicit deliverable-language requests and exact supplied artwork copy separate from conversation language. Do not translate or rewrite public source files to localize a session.1314## When To Use1516Use this skill when a workflow depends on public facts, source-backed claims,17tool or platform limits, technical capability checks, product evidence, market18context, competitor references, or uncertainty that could affect final output.19Use it before copy, prompt packs, tool routing, QA, or delivery when accuracy is20material.2122## Inputs2324- Brief, question, claim, assumption, or decision that needs verification.25- Available sources, user-provided references, repo files, screenshots, or26 public links.27- Freshness requirement, jurisdiction, market, platform, model, or tool scope.28- Required output format such as Evidence Note, claim ledger, or decision note.29- Current tool availability, including whether web browsing is actually30 available in the host environment.3132## Outputs3334- Evidence Note with verified facts, source boundaries, uncertainty, and next35 decisions.36- Claim ledger entries for approved, unsupported, conflicting, or blocked37 statements.38- Tool-limit notes for `tool-routing-cost`, prompt packs, or QA.39- Author-boundary notes that distinguish user-provided first-hand facts from40 unsupported personal or social-proof claims.41- Handoff notes for `brief-architect`, `reference-curator`, `copy-voice`,42 `instruction-packet-factory`, `qa-iteration`, or `delivery-documentation`.4344## Process45461. State the exact claim, decision, or assumption being checked.472. Identify source type: user-provided, local repo, official docs, public web,48 or unavailable.493. Verify current or unstable facts from reliable sources when browsing is50 available.514. Separate confirmed facts from inference, opinion, and missing evidence.525. Record conflicts, stale sources, unavailable sources, and confidence limits.536. For ready-to-use copy, state whether each material claim, quote, result,54 testimonial, first-hand observation, or personal statement is user-provided,55 verified, unresolved, or prohibited.567. Convert evidence into a compact decision note for the next workflow role.5758## Decision Rules5960- Prefer primary sources, official docs, repo files, and user-provided source61 truth over summaries.62- If browsing is unavailable, do not claim live verification; mark the evidence63 path as unavailable or user-provided only.64- If a fact is time-sensitive, high-stakes, legal, financial, medical, pricing,65 model-capability, or policy-related, require a freshness check before final66 use.67- If evidence conflicts, route to `qa-iteration` with the conflict and proposed68 resolution options.6970## Guardrails7172- Do not fabricate citations, links, quotes, benchmarks, capabilities, or73 release status.74- Do not use API keys, paid provider calls, hidden web automation, uploads, or75 private cloud links.76- Do not store raw private project context in public artifacts.77- Do not turn evidence notes into long research dumps; preserve only what the78 next role needs.79- Do not infer an author's experience, beliefs, emotions, or history from a80 writing preference or a generic brief.8182## Handoff8384Review gate: `evidence_fit`.8586Hand verified facts and unresolved risks to `brief-architect`, `copy-voice`,87`tool-routing-cost`, `instruction-packet-factory`, `qa-iteration`, or88`delivery-documentation`. When sources are missing, stop with a clear blocker89instead of allowing unsupported claims downstream.9091## QA Checklist9293- Checked item is explicit.94- Source type and freshness boundary are stated.95- Facts, inferences, and unknowns are separated.96- Unsupported claims are not promoted to final copy or prompts.97- Conflicts and missing evidence have a next action.98- Handoff includes only compact, usable evidence.