Name: syncplay-mobile
Author: yuroyami

Imported from yuroyami/syncplay-mobile (AGENTS.md). Install upstream with npx skills add yuroyami/syncplay-mobile. Copyright stays with the author.

AGENTS.md

This project keeps its knowledge in two files. Neither is generated, so both can go stale; the rule is that a change updates the file it touches in the same commit. This file used to be a third copy and drifted badly, which is why it is a pointer now.

File	What is in it
`CLAUDE.md`	The architecture map. Module and build structure, the Syncplay wire protocol, the sync algorithm, every subsystem, the expect/actual table, the player engines, the built in server, known gaps. Read this to understand how the app works.
`MASTER_LEDGER.md`	The engineering ledger. Every open defect with its status, the standing owner rulings you must not undo, the do-not-re-flag and refuted lists, the GitHub issue map, the roadmap and the test plan. Read this before changing anything. It is gitignored, so it exists only on the maintainer's machine.

If you are an AI agent working in this repo: read CLAUDE.md first, then MASTER_LEDGER.md if it is present. Read both in full. Do not skim.

This file used to be a full copy of CLAUDE.md. It went stale, so it became a pointer instead.

# 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 syncplay-mobile 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": "yuroyami-syncplay-mobile-syncplay-mobile", "kind": "skill", "name": "syncplay-mobile", "description": "This project keeps its knowledge in two files. Neither is generated, so both can go stale; the rule is that a change updates the file it touches in the same commit. This file used to be a third copy and drifted badly, which is why it is a pointer now.", "publisher": "yuroyami", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "This project keeps its knowledge in two files. Neither is generated, so both can go stale; the rule is that a change updates the file it touches in the same commit. This file used to be a third copy and drifted badly, which is why it is a pointer now." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/yuroyami/syncplay-mobile", "path": "AGENTS.md", "ref": "302670c6272721ae7e227dd17439ac0c9fc2280c", "url": "https://github.com/yuroyami/syncplay-mobile/blob/302670c6272721ae7e227dd17439ac0c9fc2280c/AGENTS.md", "key": "yuroyami/syncplay-mobile/AGENTS.md" } }, "instructions": "# AGENTS.md\n\nThis project keeps its knowledge in two files. Neither is generated, so both can go stale; the\nrule is that a change updates the file it touches in the same commit. This file used to be a\nthird copy and drifted badly, which is why it is a pointer now.\n\n| File | What is in it |\n|---|---|\n| `CLAUDE.md` | The architecture map. Module and build structure, the Syncplay wire protocol, the sync algorithm, every subsystem, the expect/actual table, the player engines, the built in server, known gaps. Read this to understand how the app works. |\n| `MASTER_LEDGER.md` | The engineering ledger", "cost": { "context_tokens": 280 } }

syncplay-mobile

About

AGENTS.md

Use it

Install syncplay-mobile and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews