control-kody

Drive and verify the Kody app with a Feature Map and one CLI. Use when changing UI, account routes, preview deploys, or proving a Cloud Agent change with a real origin, session, and /health SHA.

Install
npx skills add 'https://github.com/kentcdodds/kody/tree/main/.agents/skills/control-kody'
Download bundle ↓
main · 8beb6cdScanned 2026-09-15

Contributors

GitHub-linked commit authors for this SKILL.md at the saved revision. Co-authors and history before file renames are not included.

File history ↗
View on GitHub
← Back to SKILL.md

Community listings and profiles

Public catalog and owner-scoped package URLs. Public and private packages share the same /@username/:kodyId surface; visibility is the only gate.

How to get there

/community/@username/kody-id. Human share URL: /@username/kody-id (never construct /community/{listing_id} for people). Files: /@username/kody-id/tree/:ref (:ref is the repo default-branch name, a SHA, or another branch — leftover /files and HEAD 301 there). Media in that tree previews from /@username/kody-id/raw/:ref/…. Owner settings: /@username/kody-id/settings. Profile: /@username.

Drive it

node tools/control-kody.ts request GET /community.json --skip-login

APIs

  • GET /community.json
  • GET /community/:listingId.json
  • GET /profiles/:username.json
  • GET /profiles/:username/packages/:kodyId.json
  • GET /profiles/:username/packages/:kodyId/files.json
  • POST /community/:listingId/{report,feature,install}.json
  • POST /community/:listingId/trust.json returns 410 (no trusted-listing mark)

Gotchas

  • Profiles are public catalogs (packages, ratings, forks). There is no follow graph, bookmark-star, or social timeline.
  • Files, tree, and raw media URLs are public read for listed packages and owner-only for private ones. /raw/ only serves allowlisted sniffed media (never HTML or JS).
  • README ![alt](./docs/poster.png) images render from /@owner/<package-name-leaf>/assets/… (or /community/:listingId/assets/… when the leaf is a reserved ingress segment) only when the viewed README commit is the published or pinned blob /assets/ serves. Remote image URLs stay links.
  • Package settings 404 for anyone who is not the owner.
  • Official @kody/* listings skip the install confirm; third-party listings ask once (acknowledged: true or the install endpoint responds 409).
  • Admin featured is editorial catalog placement on /community and listing detail (and slim names in the onboarding persist-prompt payload). It is not a wizard Step 2 card.
  • Fork pills are Fork outdated when the listing pin is not an ancestor of the fork tip, or Fork ahead when that pin is already in the fork history (website UI only). SHA inequality alone is not enough. That is separate from HEAD ahead of published on the package Repo tab.
  • Own-profile Needs republish (listing=ahead) is listing pin behind published_commit. Guests do not see that filter.