openhands/evidence-based-citations
skills/evidence-based-citations/SKILL.md
Back factual claims and field values with official, verifiable sources. Use when the user asks to fill fields, answer questions, or make claims that must be supported by an exact quote and an official link.
$ install --global
skillsauthnpx skillsauth add openhands/extensions evidence-based-citationsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 4, 2026, 7:52 AM191.1s2 files scanned
SKILL.md
- name:
- evidence-based-citations
- description:
- Back factual claims and field values with official, verifiable sources. Use when the user asks to fill fields, answer questions, or make claims that must be supported by an exact quote and an official link.
The user wants every field value or factual claim you produce in the current response to be backed by an official, verifiable source. Apply this skill to the response that triggered it; do not assume it stays active for the rest of the conversation unless the user clearly asks for it to.
Output format
For each field or claim, respond with exactly these four labeled lines:
- Field: the field name (or a short description of the claim)
- Value: the value you are assigning (or the claim itself)
- Quote: the exact verbatim text from the source that supports the value
- Source: the official URL where the quote can be found
When there are multiple fields, repeat the block once per field. Keep blocks separated by a blank line.
Source selection rules
- Prefer primary sources, in this order:
- Official product / project documentation
- Standards documents (RFCs, W3C specs, ISO standards)
- Official API references
- Source code in the project's own repository
- Accept secondary sources (blog posts, Stack Overflow, forum threads, news articles, third-party tutorials) only as a last resort, and clearly label them as such in Source.
- The Quote field must contain text that actually appears at the Source URL. Do not paraphrase inside the quote, and do not stitch together text from different parts of the page without making the cut explicit (e.g. with
…). - If you cannot find an official source for a value, say so explicitly:
- Source:
No official source found.Then either omit the value, mark it as unverified, or ask the user how to proceed. Never invent a quote or URL.
- Source:
When to fetch
- If you have a browser / fetch tool available, retrieve the source page and copy the quote directly from it before responding.
- If you do not have a fetch tool, always respond with
Source: No official source found.rather than citing URLs from memory. LLMs cannot reliably verify URL accuracy or quote fidelity without actually fetching the page, even when a URL feels familiar.
Example
User: What HTTP status code indicates a successful request, per the HTTP semantics RFC?
- Field: HTTP status code for a successful request (per RFC 9110)
- Value: 200 (OK)
- Quote: "The 200 (OK) status code indicates that the request has succeeded."
- Source: https://www.rfc-editor.org/rfc/rfc9110.html#section-15.3.1
What this skill is not
- It is not a general "be careful with facts" reminder. Apply the strict four-field format only when the user has invoked this skill or is clearly asking for evidence-backed answers.
- It does not change how you write code, edit files, or run tools. It only governs how you report values and claims back to the user.
Related Skills
openhands/iterate
tools
VerifiedTrustedCommunity
Iterate on a GitHub pull request — drive it through CI, code review, and QA until it is merge-ready. Poll verification layers with `gh` CLI, diagnose and fix CI failures, address review feedback, retry flaky checks, push fixes, and repeat. The agent is the orchestration loop.
125SKILL.mdUpdated Apr 18, 2026
openhands/technical-writing
development
VerifiedTrustedCommunity
Guides technical explanations toward flowing, direct, conversational prose. This skill should be used for engineering chat, design discussion, architecture analysis, code-review explanations, and technical recommendations that should be concise without becoming fragmented or vague.
124SKILL.mdUpdated Jul 13, 2026
openhands/jira-issue-to-pr
tools
VerifiedTrustedCommunity
This skill should be used when the user asks to "set up a Jira automation to create pull requests", "poll Jira for create-pr issues", "automatically create GitHub PRs from Jira tickets", "deploy a Jira issue-to-PR automation", "create a Jira to GitHub PR workflow", or mentions automating GitHub PR creation from a Jira label. Deploys a cron-based OpenHands automation that watches a Jira Cloud project for issues labeled with a configurable label (default: "create-pr") and spawns an agent conversation to create a GitHub pull request for each new issue found. The target GitHub repository is read from the body of the Jira ticket - no repo parameter is required at deploy time.
123SKILL.mdUpdated Jul 7, 2026
openhands/openhands-automation
tools
VerifiedTrustedCommunity
This skill should be used when the user asks to "create an automation", "schedule a task", "set up a cron job", "webhook integration", "event-triggered automation", or mentions automations, scheduled tasks, cron scheduling, or webhook events in OpenHands Cloud.
123SKILL.mdUpdated Apr 24, 2026