references/features/community.md
references/features/community.mdBrowse 27 files
625 tokens
2,488 bytes
Token encoding: o200k_base
Snapshot 8beb6cd
← 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.jsonGET /community/:listingId.jsonGET /profiles/:username.jsonGET /profiles/:username/packages/:kodyId.jsonGET /profiles/:username/packages/:kodyId/files.jsonPOST /community/:listingId/{report,feature,install}.jsonPOST /community/:listingId/trust.jsonreturns 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
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: trueor the install endpoint responds409). - Admin featured is editorial catalog placement on
/communityand 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 behindpublished_commit. Guests do not see that filter.