Fieldops Research

Name: Fieldops Research
Author: download4you

ASecurity

Investigates externally verifiable, uncertain, current, comparative, or high-consequence questions and delivers concise, evidence-backed, actionable answers. Use when facts may have changed, claims need fact-checking, sources disagree, the user wants a recommendation or comparison (which is better, is it still true, latest version, compare X vs Y, verify this claim), or a question needs combining local evidence with official documentation, APIs, repositories, or web sources. Not for trivial s...

2 stars
0 votes
0 copies
0 views
Added September 6, 2026

ai-agentsapidocumentation

Works with

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned September 6, 2026

npx -y skills add download4you/n2-fieldops --skill fieldops-research --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Fieldops Research?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Fieldops Research

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/download4you-fieldops-research/badge)](https://www.skillsdirectory.com/skills/download4you-fieldops-research)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: fieldops-research
description: Investigates externally verifiable, uncertain, current, comparative, or high-consequence questions and delivers concise, evidence-backed, actionable answers. Use when facts may have changed, claims need fact-checking, sources disagree, the user wants a recommendation or comparison (which is better, is it still true, latest version, compare X vs Y, verify this claim), or a question needs combining local evidence with official documentation, APIs, repositories, or web sources. Not for trivial stable facts or tasks already handled by a narrower specialist skill.
---

# FieldOps Research

1. Define the decision, question, or claim that must be resolved.
2. Separate stable facts, current facts, calculations, interpretations, and unknowns.
3. Inspect user-provided and local evidence before searching externally.
4. Prefer a purpose-built connector, API, repository CLI, or official documentation.
5. Use primary sources for material claims; triangulate when consequences or conflicts
   justify it.
6. Record what is observed, inferred, calculated, and still uncertain.
7. Test calculations, links, examples, or commands when practical.
8. Lead with the answer, then give decisive evidence and the next action.

Read `references/source-strategy.md` when selecting sources and
`references/answer-contract.md` before finalizing. Do not fabricate citations or tool
access. Avoid generic caveats: if blocked, name the exact missing evidence and provide
the strongest useful conclusion or verification path available.