Name: cite-sources
Author: zx8086

Imported from zx8086/devops-incident-analyzer (agents/shared/skills/cite-sources/SKILL.md). Install upstream with npx skills add zx8086/devops-incident-analyzer --skill cite-sources. Copyright stays with the author.

Skill: Cite Sources

Purpose

Every factual claim in an analysis must be traceable to a specific tool output. This shared skill applies to the orchestrator and every sub-agent.

Procedure

When you state a finding, name the tool that produced it and the datasource it came from (e.g. "per elasticsearch_search on the prod deployment").
Include the concrete data point that supports the claim: a timestamp, a metric value, a count, an error string, or a document/record id.
When correlating across datasources, cite each contributing source separately so a reviewer can audit which evidence supports which leg of the correlation.
If a claim cannot be tied to a tool output, mark it explicitly as an inference or hypothesis, not a finding.

Rules

No uncited findings. An assertion without a tool-output citation is a defect.
Prefer the narrowest citation that supports the claim (one tool call, one record) over a vague "the logs show".
Never fabricate a citation. If you did not run the tool, do not cite it.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install cite-sources and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "zx8086-devops-incident-analyzer-cite-sources", "kind": "skill", "name": "cite-sources", "description": "Require every factual claim in an analysis to be traceable to a specific tool output -- name the tool and datasource, include the concrete supporting data point, and mark inferences explicitly as hypotheses rather than findings. Applies to the orchestrator and every sub-agent on every turn that states a finding.", "publisher": "zx8086", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Require every factual claim in an analysis to be traceable to a specific tool output -- name the tool and datasource, include the concrete supporting data point, and mark inferences explicitly as hypotheses rather than findings. Applies to the orchestrator and every sub-agent on every turn that states a finding." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/zx8086/devops-incident-analyzer", "path": "agents/shared/skills/cite-sources/SKILL.md", "ref": "4ed327ea968dc33818f87937b979f6b5c2bc5204", "url": "https://github.com/zx8086/devops-incident-analyzer/blob/4ed327ea968dc33818f87937b979f6b5c2bc5204/agents/shared/skills/cite-sources/SKILL.md", "key": "zx8086/devops-incident-analyzer/agents/shared/skills/cite-sources/SKILL.md" } }, "instructions": "# Skill: Cite Sources\n\n## Purpose\nEvery factual claim in an analysis must be traceable to a specific tool output.\nThis shared skill applies to the orchestrator and every sub-agent.\n\n## Procedure\n1. When you state a finding, name the tool that produced it and the datasource\n it came from (e.g. \"per `elasticsearch_search` on the prod deployment\").\n2. Include the concrete data point that supports the claim: a timestamp, a metric\n value, a count, an error string, or a document/record id.\n3. When correlating across datasources, cite each contributing source separately\n so a reviewer can audit", "cost": { "context_tokens": 262 } }

cite-sources

About

Skill: Cite Sources

Purpose

Procedure

Rules

Use it

Install cite-sources and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews