Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
photo-clear - Prompt - OpenSmartRoute
Promptv1.0.0
photo-clear
Clear a photograph for the book — the go/no-go gate on image rights, licensing, and caption juxtaposition. Owned by Nancy.
Prompt file imported from xiaolai/no-one-did-it (.claude/commands/photo-clear.md). Copyright stays with the author.
Photo Clear
Dispatch the nancy-legal-risk-counsel agent with task: run the go/no-go clearance gate on a proposed photograph — rights, permissions, licensing, and caption juxtaposition — using defamation-wording and citation-hygiene.
Nancy is the single gate-owner: no photo ships without her clearance. Verify (a) the image's rights status (public domain / licensed / fair-use basis) and that permission is recorded in the source-ledger row, as for a quote under rule 06; and (b) that the caption and the photo's placement do not imply a chain the record does not support — juxtaposition carries rule-07 implication burden even when no verb overclaims. The feeders are upstream: the domain researcher sources candidates, Stephen verifies provenance (is this genuinely a photo of the event it claims to depict?), and Wayne drafts the caption. Compositing several images into one is a human production step outside the crew. End with a clear go or no-go and, on no-go, the specific defect (rights gap, provenance gap, or juxtaposition risk) and its owner. Photos live in book/evidence/photos/. See rule 03 "Visual material ownership."
If invoked without a target, return: "Name the photo and where it goes (e.g. /photo-clear 08 detainee-photo-abu-ghraib)." Do not clear an unnamed image.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# Photo Clear
Dispatch the `nancy-legal-risk-counsel` agent with task: run the go/no-go clearance gate on a proposed photograph — rights, permissions, licensing, and caption juxtaposition — using `defamation-wording` and `citation-hygiene`.
Nancy is the single gate-owner: no photo ships without her clearance. Verify (a) the image's rights status (public domain / licensed / fair-use basis) and that permission is recorded in the source-ledger row, as for a quote under rule 06; and (b) that the caption and the photo's placement do not imply a chain the record does not support — juxtaposition carries rule-07 implication burden even when no verb overclaims. The feeders are upstream: the domain researcher sources candidates, Stephen verifies provenance (is this genuinely a photo of the event it claims to depict?), and Wayne drafts the caption. Compositing several images into one is a human production step outside the crew. End with a clear go or no-go and, on no-go, the specific defect (rights gap, provenance gap, or juxtaposition risk) and its owner. Photos live in `book/evidence/photos/`. See rule `03` "Visual material ownership."
If invoked without a target, return: "Name the photo and where it goes (e.g. /photo-clear 08 detainee-photo-abu-ghraib)." Do not clear an unnamed image.
<example>
Context: Chapter 08 proposes a wire-service photo of a named official beside a podium, captioned to sit next to the claim that the official authorized the policy.
user: /photo-clear 08 official-at-podium
assistant: Returns no-go: the caption's placement beside the authorization claim implies the official ordered the policy, which the record does not establish (rule 07); rights status is also unconfirmed. Specifies Stephen to confirm provenance and date, Wayne to re-caption to the documented fact only, and the researcher to obtain the wire-service license. Re-request after the three feeders clear.
</example>
<example>
Context: A US-government public-domain photo with a neutral, documented caption is proposed.
assistant: Returns go: image is US-government public domain (no license needed), provenance confirmed by Stephen, caption states only the documented event. Records the public-domain basis in the source-ledger row and notes no juxtaposition risk.
</example>
Installed into a catalogue, chosen by a router
Install photo-clear 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.
{
"prompt": "# Photo Clear\n\nDispatch the `nancy-legal-risk-counsel` agent with task: run the go/no-go clearance gate on a proposed photograph — rights, permissions, licensing, and caption juxtaposition — using `defamation-wording` and `citation-hygiene`.\n\nNancy is the single gate-owner: no photo ships without her clearance. Verify (a) the image's rights status (public domain / licensed / fair-use basis) and that permission is recorded in the source-ledger row, as for a quote under rule 06; and (b) that the caption and the photo's placement do not imply a chain the record does not support — juxtaposition carries rule-07 implication burden even when no verb overclaims. The feeders are upstream: the domain researcher sources candidates, Stephen verifies provenance (is this genuinely a photo of the event it claims to depict?), and Wayne drafts the caption. Compositing several images into one is a human production step outside the crew. End with a clear go or no-go and, on no-go, the specific defect (rights gap, provenance gap, or juxtaposition risk) and its owner. Photos live in `book/evidence/photos/`. See rule `03` \"Visual material ownership.\"\n\nIf invoked without a target, return: \"Name the photo and where it goes (e.g. /photo-clear 08 detainee-photo-abu-ghraib).\" Do not clear an unnamed image.\n\n<example>\nContext: Chapter 08 proposes a wire-service photo of a named official beside a podium, captioned to sit next to the claim that the official authorized the policy.\nuser: /photo-clear 08 official-at-podium\nassistant: Returns no-go: the caption's placement beside the authorization claim implies the official ordered the policy, which the record does not establish (rule 07); rights status is also unconfirmed. Specifies Stephen to confirm provenance and date, Wayne to re-caption to the documented fact only, and the researcher to obtain the wire-service license. Re-request after the three feeders clear.\n</example>\n\n<example>\nContext: A US-government public-domain photo with a neutral, documented caption is proposed.\nassistant: Returns go: image is US-government public domain (no license needed), provenance confirmed by Stephen, caption states only the documented event. Records the public-domain basis in the source-ledger row and notes no juxtaposition risk.\n</example>",
"variables": [],
"notes": "Clear a photograph for the book — the go/no-go gate on image rights, licensing, and caption juxtaposition. Owned by Nancy. Researchers source, Stephen verifies provenance, Wayne captions; compositing is a human production step. See rule 03 \"Visual material ownership.\" Arguments: <image-or-chapter-and-subject>.",
"metadata": {
"source": {
"provider": "github-claude-commands",
"repository": "https://github.com/xiaolai/no-one-did-it",
"path": ".claude/commands/photo-clear.md",
"ref": "b5e9c8f820bc04bb1d452d4109318673c08c3945",
"url": "https://github.com/xiaolai/no-one-did-it/blob/b5e9c8f820bc04bb1d452d4109318673c08c3945/.claude/commands/photo-clear.md",
"key": "xiaolai/no-one-did-it/.claude/commands/photo-clear.md"
}
}
}
Fetch it by URL: GET /api/v1/registry/xiaolai-no-one-did-it-photo-clear-command/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
