agentsclimarketplace

Aikc open source release

Skill AHappyAtlas/ai-knowledge-center/ai-knowledge/skills/aikc-open-source-release

Local-first project context, verification gates, and repo-scoped MCP for coding agents.From the repository description

Install
npx -y skills add AHappyAtlas/ai-knowledge-center --skill aikc-open-source-release

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 26 days oldThe repository was created 26 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, 489 tokens by cl100k_base, as published. Nobody here has run it

AIKC Open-Source Release Skill

Use this skill when preparing AI Knowledge Center for a public GitHub or npm release, or when validating release readiness after package, CLI, security, community, or documentation changes.

Release Contract

  • License, contribution guide, security policy, code of conduct, changelog, issue templates, and CI must be present before a first public release.
  • Preserve local-first defaults: 127.0.0.1, repository-scoped MCP, allowlisted commands, and telemetry opt-out with AIKC_TELEMETRY_EXPORTER=none.
  • Release notes must include user-visible changes, upgrade notes, rollback version, validation evidence, and supported platforms.
  • The published CLI must expose aikc doctor --json and aikc context-pack --project <path> --task <task> as direct verification and context-routing entrypoints.
  • Never print or commit npm tokens, .env.local, private project content, or user registry data.

Validation

Run from the package repository:

node ai-knowledge/scripts/doctor.cjs --json
node ai-knowledge/scripts/eval-workflow.cjs
node ai-knowledge/scripts/code-review.cjs
node ai-knowledge/scripts/knowledge-check.cjs
npm run typecheck
npm run lint
npm run build
npm pack --dry-run
npm run smoke:package

smoke:package packs the built package, installs it in a clean local temporary directory and a temporary npm global prefix, initializes projects through both install modes, and runs doctor plus context-pack. It must use an isolated AIKC_HOME and remove its temporary package and state after completion.

Platform Boundary

  • Local host: Windows, macOS, or Linux. The smoke script must handle the local npm launcher safely on each platform.
  • Remote target: GitHub Actions runners on Windows, macOS, and Linux. CI must run the same package smoke test across that matrix.
  • No remote shell, SSH, production deployment, or broadened network binding is part of release preparation.

Publish

Use docs/release-checklist.md for the human publish sequence. Publishing and creating a GitHub Release require explicit maintainer authority; do not attempt them merely because the checks pass.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most ship operate skills give in 489 tokens

Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07

  • Document a rollback plan before deploymentin 41 of 779, across 22 files
  • Update the changelogin 21 of 779, across 19 files
  • Run the test suitein 20 of 779
  • Create an annotated git tagin 20 of 779
  • Clean up feature flags after full rolloutin 18 of 779, across 10 files
  • Verify deployment health after launchin 18 of 779, across 10 files
  • Test both feature flag statesin 17 of 779, across 9 files
  • Verify the working tree is cleanin 17 of 779
  • Make database migrations backward-compatiblein 16 of 779, across 8 files
  • Set up error monitoring before launchin 15 of 779, across 7 files
  • Monitor metrics at each rollout stagein 14 of 779, across 5 files
  • Create a GitHub releasein 14 of 779

Said here and by no other author read

  • include required governance and CI files before first release
  • preserve local-first defaults and telemetry opt-out
  • include user-visible changes and rollback version in release notes
  • expose doctor and context-pack entrypoints in the CLI
  • run doctor, eval, review, and knowledge validation scripts
  • run matrix smoke tests across Windows, macOS, and Linux

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,835. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.