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.
repeat-resistant-briefs - Skill - OpenSmartRoute
Skillv1.0.0
repeat-resistant-briefs
Use when a recurring report or newsletter keeps resurfacing the same links, repos, or themes. Build a deterministic source pack with canonical identities, recent delivery history, justified follow-ups
Imported from sapochat/repeat-resistant-briefs (SKILL.md). Install upstream with npx skills add sapochat/repeat-resistant-briefs. Copyright stays with the author (MIT).
Repeat-Resistant Briefs
Collect raw sources deterministically.
Normalize URLs and stable item identifiers.
Parse recent delivered outputs—not only raw candidate history.
Suppress items seen in the configured window unless a concrete follow-up reason exists.
Apply quality and relevance floors before source diversity.
Build a visible source pack containing candidates, recent-history warnings, and editorial rules.
Let a human or model synthesize only from the source pack.
QA the delivered response separately from prompt and collector wrappers.
Feed delivered identities back into history.
Do not use rigid source quotas to promote weak material. It is valid for a section or source to contribute zero items.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# 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}'
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
{
"ocm": "1",
"id": "sapochat-repeat-resistant-briefs-repeat-resistant-briefs",
"kind": "skill",
"name": "repeat-resistant-briefs",
"description": "Use when a recurring report or newsletter keeps resurfacing the same links, repos, or themes. Build a deterministic source pack with canonical identities, recent delivery history, justified follow-ups, and quality-first selection.",
"publisher": "sapochat",
"version": "1.0.0",
"capabilities": {
"domains": [
"customer_support",
"marketing"
],
"tags": [
"skill-md",
"github"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Use when a recurring report or newsletter keeps resurfacing the same links, repos, or themes. Build a deterministic source pack with canonical identities, recent delivery history, justified follow-ups, and quality-first selection."
],
"primary": false,
"metadata": {
"source": {
"provider": "github",
"repository": "https://github.com/sapochat/repeat-resistant-briefs",
"path": "SKILL.md",
"ref": "5c3a35f5b9fa92306841badcd7da0e4c7dff050a",
"url": "https://github.com/sapochat/repeat-resistant-briefs/blob/5c3a35f5b9fa92306841badcd7da0e4c7dff050a/SKILL.md",
"key": "sapochat/repeat-resistant-briefs/SKILL.md"
},
"license": "MIT"
},
"instructions": "# Repeat-Resistant Briefs\n\n1. Collect raw sources deterministically.\n2. Normalize URLs and stable item identifiers.\n3. Parse recent delivered outputs—not only raw candidate history.\n4. Suppress items seen in the configured window unless a concrete follow-up reason exists.\n5. Apply quality and relevance floors before source diversity.\n6. Build a visible source pack containing candidates, recent-history warnings, and editorial rules.\n7. Let a human or model synthesize only from the source pack.\n8. QA the delivered response separately from prompt and collector wrappers.\n9. Feed delivered identiti",
"cost": {
"context_tokens": 185
}
}
Fetch it by URL: GET /api/v1/registry/sapochat-repeat-resistant-briefs-repeat-resistant-briefs/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.