How do I install the Aget Document Finding skill?

Run npx skillmds@latest add tomevault-io/aget-document-finding in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Aget Document Finding skill do?

Document research findings with evidence Use when this capability is needed. It is listed under Research & Search on SkillMD.

Is Aget Document Finding safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Aget Document Finding?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Aget Document Finding free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Aget Document Finding?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Aget Document Finding by tomevault-io

Name: Aget Document Finding
Author: tomevault-io

File contents

aget-document-finding

Document research findings with evidence, methodology, and implications. Creates structured finding documents for knowledge capture.

Instructions

When this skill is invoked:

Formulate Finding
- Clear, specific statement
- Falsifiable where possible
- Scoped appropriately
Document Evidence
- Primary sources
- Data/observations
- Chain of reasoning
Describe Methodology
- How finding was reached
- Tools/techniques used
- Reproducibility notes
Articulate Implications
- What this means
- Recommended actions
- Future research directions
Note Limitations
- Scope boundaries
- Confidence level
- Known gaps

Output Format

# Research Finding: [Title]

**Date**: [YYYY-MM-DD]
**Researcher**: [Agent Name]
**Status**: [Draft/Reviewed/Accepted]
**Confidence**: [High/Medium/Low]

---

## Finding Statement

[Clear, specific, falsifiable statement of what was discovered]

---

## Evidence

### Primary Sources
1. [Source 1]: [What it shows]
2. [Source 2]: [What it shows]

### Data/Observations
- [Observation 1]
- [Observation 2]

### Reasoning Chain
1. [Premise 1]
2. [Premise 2]
3. Therefore: [Conclusion]

---

## Methodology

**Approach**: [Description of method]

**Tools Used**:
- [Tool 1]
- [Tool 2]

**Reproducibility**: [How to reproduce this finding]

---

## Implications

### Immediate
- [Implication 1]

### Strategic
- [Longer-term implication]

### Recommended Actions
1. [Action 1]
2. [Action 2]

---

## Limitations

1. [Limitation 1]: [How it affects conclusions]
2. [Limitation 2]: [How it affects conclusions]

---

## Future Research

- [Question raised by this finding]

---

## References

1. [Citation 1]

Constraints

C1: NEVER document findings without evidence — findings must be supported
C2: NEVER overstate confidence level — epistemic humility required
C3: NEVER omit contradictory evidence — complete picture enables sound judgment

SKILL-030: aget-document-finding specification
ONTOLOGY_researcher.yaml: Finding, Evidence, Hypothesis concepts
CAP-RES-002: Finding Documentation capability

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: aget-document-findingdescription: Document research findings with evidence Use when this capability is needed.---# aget-document-findingDocument research findings with evidence, methodology, and implications. Creates structured finding documents for knowledge capture.## InstructionsWhen this skill is invoked:1. **Formulate Finding** - Clear, specific statement - Falsifiable where possible - Scoped appropriately2. **Document Evidence** - Primary sources - Data/observations - Chain of reasoning3. **Describe Methodology** - How finding was reached - Tools/techniques used - Reproducibility notes4. **Articulate Implications** - What this means - Recommended actions - Future research directions5. **Note Limitations** - Scope boundaries - Confidence level - Known gaps## Output Format```markdown# Research Finding: [Title]**Date**: [YYYY-MM-DD]**Researcher**: [Agent Name]**Status**: [Draft/Reviewed/Accepted]**Confidence**: [High/Medium/Low]---## Finding Statement[Clear, specific, falsifiable statement of what was discovered]---## Evidence### Primary Sources1. [Source 1]: [What it shows]2. [Source 2]: [What it shows]### Data/Observations- [Observation 1]- [Observation 2]### Reasoning Chain1. [Premise 1]2. [Premise 2]3. Therefore: [Conclusion]---## Methodology**Approach**: [Description of method]**Tools Used**:- [Tool 1]- [Tool 2]**Reproducibility**: [How to reproduce this finding]---## Implications### Immediate- [Implication 1]### Strategic- [Longer-term implication]### Recommended Actions1. [Action 1]2. [Action 2]---## Limitations1. [Limitation 1]: [How it affects conclusions]2. [Limitation 2]: [How it affects conclusions]---## Future Research- [Question raised by this finding]---## References1. [Citation 1]```## Constraints- **C1**: NEVER document findings without evidence — findings must be supported- **C2**: NEVER overstate confidence level — epistemic humility required- **C3**: NEVER omit contradictory evidence — complete picture enables sound judgment## Related- SKILL-030: aget-document-finding specification- ONTOLOGY_researcher.yaml: Finding, Evidence, Hypothesis concepts- CAP-RES-002: Finding Documentation capability---> Converted and distributed by [TomeVault](https://tomevault.io/claim/aget-framework) — claim your Tome and manage your conversions.

Frequently asked questions

Aget Document Finding