Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

feat(evolution): private reviewed overlay revisions from local session-derived skill improvements

オープン
#56 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@mrgoonie がすでに取り組んでいます。

2026年10月14日 から。

  • #83 @mrgoonie による — オープン

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
20/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
typescript

調査の方向性

Read the current schema, auth, routes, and contracts, then review issues #31, #34, #35, and #55 for prerequisites and existing patterns. The issue scopes implementation to backend contracts and CLI helpers, with schema validation and negative security tests first. Done means the reviewed private overlay flow meets the listed privacy, lineage, authorization, concurrency, and rollback requirements; no specific files or tests are named.

索引モデルが issue の本文から書いたものです。

説明

enhancement

Parent / prerequisites

Tracked by SkillX #31. Depends on personal-kit immutable lineage/overlay #55, registry releases #34/#54. Consumer AgentKit #2274, future AK ak insights -> skill improvement proposal and private publish.

Objective

Expose an authenticated, privacy-safe flow to publish user-reviewed skill overlay revisions created from local AgentKit session analysis, while preserving base foundation ancestry, source-license/entitlement restrictions, review history, optimistic concurrency and no raw session exfiltration.

Contract

  1. Inputs: target @publisher/skill, base package ID/version/digest, existing overlay revision/generation, candidate structural patch and supporting non-sensitive evidence summary; never require or accept raw transcripts, environment secrets, local absolute filesystem paths, prompts containing customer data or arbitrary source trees without specific consent.
  2. An optional local agent may analyze session/evaluation and propose a patch, but only user-authorized content is sent. Default visibility private; profile settings do not grant automatic publish permission.
  3. Validate package schema, patch bounds, AST/semantic extension points, submitted file paths, content scanner, license, foundation redistribution restrictions, publisher namespace, entitlements, declared required runtime permissions and resource manifests. Reject hidden binary/executable additions unless separately declared/reviewed.
  4. Immutable revision with revision ID, parent digest, content digest, base digest, ancestry chain, author and audit metadata. Compare-and-swap expectedGeneration and idempotency key to prevent lost updates and duplicate publish.
  5. Distinguish draft, candidate, reviewed, published, rejected, and quarantined as needed without conflicting with package release states. Disallow publish based purely on an unverifiable success counter or self-reported prompt.
  6. User explicitly approves diff + permissions + target visibility; record consent/approval proof, not private session content. Provide dry-run validation endpoint and machine-readable conflicts/new permission requests.
  7. Support rollback to previous revision and local locked sync; old revision remains available under policy when newer candidate rejected. Handle private/public transitions without exposing paid upstream contents.
  8. Reuse existing skillx publish / registry auth patterns and #55 lineage API; do not build a new service or second user identity.

Adversarial acceptance

  • No raw transcript fields or secrets accidentally persisted, logged, vectorized, indexed or included in errors.
  • Anonymous/other-user writer denied; wrong base digest/entitlement/visibility rejected; concurrent proposals conflict explicitly.
  • Double-submit of same revision is idempotent; differing content under same immutable revision refused.
  • Paid/private upstream derivative cannot leak protected foundation bytes through public patch/preview/search.
  • Review denial, compromised account, quarantined content, rollback, retry and expired credentials deterministic.
  • Works with manifest and locked sync from #55, and AK publishes only reviewed effective user-owned delta.

Agent implementation prompt

Read SkillX instructions and current schema/auth/routes/contracts plus #31/#34/#35/#55 before coding. Specify threat/privacy model and the exact acceptable request envelope; add schema validation tests first. Prefer a local-only evidence proposal and upload patch only. Implement a dry-run validate step, CAS-backed versioned persistence and explicit approval endpoint with audit, strict publisher and paid-license checks. Add negative security tests (accidental secret/session upload, cross-user access, unauthorized visibility, lost update) and backward compatibility coverage. Scope the PR to backend/contracts/CLI helpers; downstream AgentKit session parsing and eval stay in AgentKit. Include migrations, rollback and exact tests in PR.

Non-goals

Reading or indexing full user sessions server-side, training on private transcripts, automatic unattended publish, crypto payments/creator settlements, automatic security approval.

主要言語
TypeScript
スター
186
フォーク
40
平均マージ
10時間 12分
マージ済み PR(30日)
16

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

nextlevelbuilder/skillx のほかの issue

nextlevelbuilder/skillx の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。