signalproof-research

Conducts evidence-controlled research with source classification, contradiction tracking, and decision-ready handoffs.

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/docreo/Signalproof-Skills --skill signalproof-research-docreo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: signalproof-research
Source: https://github.com/docreo/Signalproof-Skills/tree/main/skills/signalproof-research
Command: npx skills add https://github.com/docreo/Signalproof-Skills --skill signalproof-research-docreo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research for technical decisions often produces link dumps, stale facts, or vendor claims treated as verified truth, leading to poor adoption choices. This Skill enforces a bounded research contract that separates source-backed facts from inference, preserves contradictions, and stops discovery from silently becoming implementation. ## Core Features & Use Cases - Claim Classification: Labels every material claim as source-backed fact, cross-source fact, vendor claim, inference, proposal, or unknown/conflicted. - Source Quality & Freshness Control: Prioritizes primary sources, checks version/date context for unstable facts, and prevents mirrors or syndicated copies from counting as independent confirmation. - Structured Research Output: Produces a decision-ready report with question, scope, findings, provenance, contradictions, unknowns, status, and a recommended handoff to evaluation, security, or planning. - Use Case: When evaluating whether to adopt a new open-source dependency, use this Skill to verify the canonical repository, maintainer, license, security advisories, and current version before any evaluation or installation decision. ## Quick Start Use the signalproof-research skill to investigate the current maintenance status, license, and security posture of the library we are considering, and return a sourced findings report with any contradictions flagged.

Frequently Asked Questions about signalproof-research

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

FAQPage Schema
How do I research a tool or library before adopting it?▼

Define the exact question, downstream decision, scope, and freshness boundary first, then gather evidence from primary sources like official documentation, canonical repositories, and license text. Classify each finding by evidence type and produce a sourced report before any evaluation or installation occurs.

How to tell vendor claims from verified facts in technical research?▼

Label vendor marketing material as a vendor claim, not an established fact, and seek independent confirmation from genuinely separate sources. Mirrors, syndicated copies, and repeated vendor material do not count as independent confirmation of a claim.

What sources should I use for technical due diligence?▼

Prefer primary sources for specifications, licenses, security advisories, releases, and APIs: official documentation, canonical repositories, standards bodies, and vendor security advisories. Use independent benchmarks and reputable reporting when external assessment is needed.

When should research stop instead of continuing?▼

Stop when the declared question is sufficiently answered for its decision boundary, or when continuing would require unauthorized access, unsafe code execution, credential exposure, or protected-data disclosure. Proportionate searching prevents scope creep beyond the original question.

What are the limitations of evidence-based research skills?▼

Research establishes what evidence supports but does not authorize adoption, installation, purchases, or deployment decisions. Those decisions belong to separate evaluation, readiness, and security disciplines that consume the research handoff.