Skip to content

chore(sdk): discovery keywords + npm publish fields (#468)#589

Merged
chronoai-shining merged 3 commits into
developfrom
chore/468-keywords-topics
May 19, 2026
Merged

chore(sdk): discovery keywords + npm publish fields (#468)#589
chronoai-shining merged 3 commits into
developfrom
chore/468-keywords-topics

Conversation

@chronoai-shining
Copy link
Copy Markdown
Collaborator

Closes #468.

What

Discovery-metadata pass on the two SDK manifests so npm + PyPI search land on the same vocabulary the project actually uses.

  • sdk/typescript/package.json — adds keywords + the npm-page fields (homepage, bugs, repository, license). private: true left alone — npm publish strategy is the scope of [Bug] SDK publish status — TS SDK has private:true, clarify npm/PyPI publication strategy #473, this PR is purely metadata.
  • sdk/python/pyproject.toml — replaces the legacy keyword set with the aligned vocabulary.
  • Keyword set across both SDKs: ornn, agent, skill-registry, skill-lifecycle, ai-agents, model-agnostic, mcp, llm, sdk.

GitHub repo topics will be set out-of-band via gh repo edit after merge:
agent, skill-registry, ai-agents, model-agnostic, mcp, bun, hono, typescript.

Test plan

  • Pure metadata — no runtime/test impact
  • CI green
  • Post-merge: confirm repo topics applied

#468 — sets keywords aligned to agent-API positioning (ornn,
agent, skill-registry, skill-lifecycle, ai-agents,
model-agnostic, mcp, llm, sdk) and the four npm publish fields
that show up on the package page (homepage, bugs, repository,
license).

private:true is preserved here; npm publish strategy is the
separate scope of #473.
#468 — replaces the legacy keyword set (skills, ai, agents, nyxid)
with the same vocabulary used across the TS SDK so PyPI search
surfaces the same intent: ornn, agent, skill-registry,
skill-lifecycle, ai-agents, model-agnostic, mcp, llm, sdk.
@chronoai-shining chronoai-shining merged commit 7523466 into develop May 19, 2026
10 checks passed
@chronoai-shining chronoai-shining deleted the chore/468-keywords-topics branch May 19, 2026 06:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Misc] Add npm/PyPI keywords + GitHub repo topics for discoverability

1 participant