Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Personal-kit API gaps for AgentKit kit publish/sync

已关闭
  • 哪里不对？
#88 1 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@mrgoonie 已经在做这个了。

开始于 2026年10月15日。

评估

这个 Issue 还没有评估数据。

描述

M0 AgentKit v3 release blocker (owner decision, 2026-10-19): Personal kits are no longer a post-v3 optional milestone. AgentKit #2524 and #2589 require production-compatible first-run flows after ak update --ssot: create/edit foundation-derived skills and personal kits, rebase/resolve, explicit private publish, locked second-device sync, and approved session-evolution proposal; local/offline use requires no SkillX login, cloud calls require scoped auth. At audit, SKILLX_PERSONAL_KITS_API=0 in apps/web/wrangler.jsonc. PR #94 delivered composition metadata and If-Match on 2026-10-16, so re-check gaps 1–2 rather than reimplement, and evaluate 3–7 against current schema. Release must pass real staging→production-compatible E2E including signed @agentkit/* foundation publishing, pinned older base handling, CAS conflict, private permissions, no secret leakage and rollback; no fake-only GO. Own exact API enablement, rollback flag and smoke receipts. AgentKit #2282 owns independent acceptance. No automatic user-session upload, public publish or execution of remote scripts. Server-side work should not duplicate AgentKit's Go installer.

Context

AgentKit G2 adds ak skills kit publish and ak skills kit sync --locked for personal kits. The work is tracked in bestagentkits/agentkit#2278 under the epic bestagentkits/agentkit#2274.

Building them against the current personal-kit API surfaced gaps that limit what a synced kit can do. AgentKit works around each one by failing safe and does not depend on any undocumented endpoint.

Gaps

  1. A revision document has no composition metadata. There is no field for the manifest's extends and include, or for the resolution records (keep-old, fork and overlay decisions). As a result, a kit synced from SkillX cannot be rebased or edited from that copy.
    • Ask: optional, schema-validated composition fields on a revision document, and include them in the document digest.
  2. No If-Match or ETag precondition on kit writes. AgentKit sends the expected generation in the request body.
    • Ask: honor If-Match: <generation> and return 412 on a mismatch, keeping the body field for compatibility.
  3. Only forks of ak- skills can be published. An in-place overlay on a foundation skill is refused, so AgentKit exits 6 for it today.
    • Ask: accept structured overlay revisions against a pinned foundation skill, using the lineage from #55.
  4. Bases are verified against SkillX releases only. The @agentkit/* foundation releases must exist on SkillX before any AgentKit kit can publish or sync.
    • Ask: publish or mirror the @agentkit/* releases, or accept a signed AgentKit release manifest as a base.
  5. Session proposals are not offered through the personal-kit API that AgentKit uses. This relates to #56.
  6. Every pinned base must be the current release. A skill pinned to an older foundation release cannot be published until it is rebased.
    • Ask: allow a revision to pin any published, non-yanked base release.
  7. extends: skillx:<kit> is not supported. A manifest cannot extend another SkillX kit yet; AgentKit keeps it marked unsupported.

Acceptance

Each item is either done or explicitly declined, with the reason. AgentKit then updates its contract and the G2 acceptance rows.

Refs #31

主要语言
TypeScript
星标
190
派生
42
平均合并
3 小时 33 分钟
30 天内合并 PR
48

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

nextlevelbuilder/skillx 的其他 Issue

查看 nextlevelbuilder/skillx 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。