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.
yatinkare.github.io - Skill - OpenSmartRoute
Skillv1.0.0
yatinkare.github.io
1. Read the new Markdown post and correct clear grammatical, spelling, punctuation, and capitalization errors while preserving the author’s voice. 2. Check the YAML header and confirm it has valid val
Imported from YatinKare/yatinkare.github.io (AGENTS.md). Install upstream with npx skills add YatinKare/yatinkare.github.io. Copyright stays with the author.
Blog publishing workflow
Read the new Markdown post and correct clear grammatical, spelling, punctuation, and capitalization errors while preserving the author’s voice.
Check the YAML header and confirm it has valid values for title, date, description, hero, heroAlt, featured, draft, and substack.
Confirm the filename is the intended URL slug and that the hero image exists at the path referenced by hero.
Set the new post’s featured value to true and set the previous featured post’s value to false.
Store the hero image in public/images/ so production builds copy it into docs/images/ and do not remove it.
Add the new post URL and its image metadata to both public/sitemap.xml and docs/sitemap.xml.
Run npm run check, npm run build, and xmllint --noout public/sitemap.xml docs/sitemap.xml.
Confirm the generated route exists under docs/blog/, and confirm the hero image still exists under both public/images/ and docs/images/ after the build.
Review git status and the complete diff. Keep unrelated user changes out of the commit.
Create a feature branch, commit the post, image, sitemap, and generated-site changes, push the branch, and open a pull request against main with the verification commands in the description.
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": "yatinkare-yatinkare-github-io-yatinkare-github-io",
"kind": "skill",
"name": "yatinkare.github.io",
"description": "1. Read the new Markdown post and correct clear grammatical, spelling, punctuation, and capitalization errors while preserving the author’s voice. 2. Check the YAML header and confirm it has valid values for `title`, `date`, `description`, `hero`, `heroAlt`, `featured`, `draft`, and `substack`. 3. Confirm the filename is the intended URL slug and that the hero image exists at the path referenced by `hero`. 4. Set the new post’s `featured` value to `true` and set the previous featured post’s value to `false`. 5. Store the hero image in `public/images/` so production builds copy it into `docs/images/` and do not remove it. 6. Add the new post URL and its image metadata to both `public/sitemap.xml` and `docs/sitemap.xml`. 7. Run `npm run check`, `npm run build`, and `xmllint --noout public/sitemap.xml docs/sitemap.xml`. 8. Confirm the generated route exists under `docs/blog/`, and confirm the hero image still exists under both `public/images/` and `docs/images/` after the build. 9. Review `git status` and the co",
"publisher": "YatinKare",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github-agents"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"1. Read the new Markdown post and correct clear grammatical, spelling, punctuation, and capitalization errors while preserving the author’s voice. 2. Check the YAML header and confirm it has valid values for `title`, `date`, `description`, `hero`, `heroAlt`, `featured`, `draft`, and `substack`. 3. Confirm the filename is the intended URL slug and that the hero image exists at the path referenced by `hero`. 4. Set the new post’s `featured` value to `true` and set the previous featured post’s value to `false`. 5. Store the hero image in `public/images/` so production builds copy it into `docs/images/` and do not remove it. 6. Add the new post URL and its image metadata to both `public/sitemap.xml` and `docs/sitemap.xml`. 7. Run `npm run check`, `npm run build`, and `xmllint --noout public/sitemap.xml docs/sitemap.xml`. 8. Confirm the generated route exists under `docs/blog/`, and confirm the hero image still exists under both `public/images/` and `docs/images/` after the build. 9. Review `git status` and the co"
],
"primary": false,
"metadata": {
"source": {
"provider": "github-agents",
"repository": "https://github.com/YatinKare/yatinkare.github.io",
"path": "AGENTS.md",
"ref": "0227f3625693710d40b15e282152ad5d7cb68487",
"url": "https://github.com/YatinKare/yatinkare.github.io/blob/0227f3625693710d40b15e282152ad5d7cb68487/AGENTS.md",
"key": "YatinKare/yatinkare.github.io/AGENTS.md"
}
},
"instructions": "# Blog publishing workflow\n\n1. Read the new Markdown post and correct clear grammatical, spelling, punctuation, and capitalization errors while preserving the author’s voice.\n2. Check the YAML header and confirm it has valid values for `title`, `date`, `description`, `hero`, `heroAlt`, `featured`, `draft`, and `substack`.\n3. Confirm the filename is the intended URL slug and that the hero image exists at the path referenced by `hero`.\n4. Set the new post’s `featured` value to `true` and set the previous featured post’s value to `false`.\n5. Store the hero image in `public/images/` so production ",
"cost": {
"context_tokens": 327
}
}
Fetch it by URL: GET /api/v1/registry/yatinkare-yatinkare-github-io-yatinkare-github-io/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.
