菜单
Kai's licensing policy - MIT for shareable, AGPL-3.0 for deployment-of-one, proprietary for private. Triggers - license, LICENSE, MIT, AGPL, GPL, copyright, SPDX, what license.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Kai's "start a sidequest" command - file a Forgejo issue from a described piece of work, then dispatch it through ward into its own session.
Tier and prune an issue backlog - P0-P4 tier definitions (P4 is the icebox/lowest tier), a target distribution as ranges, percentile-cut assignment that lands within the bands, pruning, and a second orthogonal automation-mode axis (headless/interactive/consult). Triggers - prioritize, prioritization, triage the backlog, P0/P1/P2/P3/P4, backlog ratio, icebox, burn down the backlog, tier the issues, automation mode, eligibility to dispatch.
gpg-ssm is a GPG wrapper that pulls signing material from AWS SSM at sign time instead of caching on disk. Use when wiring up a fresh machine for signed commits, bootstrapping the shared signing key, rotating a key, or debugging signing failures. Triggers - gpg-ssm, gpg signing, signed commits.
Git + GitHub umbrella. Hard rule - never use gh api graphql without double-confirming, REST is default. Owns the full PR lifecycle (branch, commit, open, monitor CI, auto-fix, merge) and routes to ward-passthrough and git-workflow siblings.
git workflow, forgejo, default tracker, commit, push, PR, gh, fj, issue, todo, gish.
Kai's technical preferences - Go CLI defaults (urfave/cli), Charm TUI stack, dead-repo check, doc conventions, default license. Triggers - cli, tui, library, dependency, recommend tool.
| name | coding-licenses |
| description | Kai's licensing policy - MIT for shareable, AGPL-3.0 for deployment-of-one, proprietary for private. Triggers - license, LICENSE, MIT, AGPL, GPL, copyright, SPDX, what license. |
How to pick a license for a coilysiren/* repo. Choose by what the repo is for, not by habit. Three tiers, most to least permissive.
Anything Kai wants other people to pick up, reuse, fork, and build on. Generic tools, libraries, helper and derivative scripts, substrate tooling that is published for reuse.
MIT.LICENSE file, MIT text, Kai's copyright line.A repo that is a deployment of one - software Kai runs as a single-tenant deployment for herself, not a library others embed. AGPL is the right tier because it closes the network-service loophole: anyone who redeploys it, modified or not, as a service must offer the source to its users. That keeps a personal deployment from being silently swallowed into someone else's closed product.
AGPL-3.0-or-later (use the full SPDX identifier, not a bare AGPL).LICENSE file with the full AGPL-3.0 text, Kai's copyright line. Set the SPDX id in package metadata (Cargo.toml license, package.json license, pyproject.toml license).galaxy-gen.The stricter-than-AGPL case: a personal repo where the intent is not "share on terms" but "this is mine, do not surface it." The honest finding is that no named open-source-style license does this - copyright licenses govern copying, modifying, and distributing, not whether someone may acknowledge the work exists. "Don't cite me, don't reference me, pretend you do not see me" is a privacy posture, not a licensable term. So tier 3 is two separate layers:
LICENSE notice (no grant of rights, copyright Kai, all rights reserved). SPDX has no open identifier for this - use LicenseRef-Proprietary or omit the SPDX field. Keep the repo private.AGENTS.md line) is tracked, not yet built - see the tracking issue.Creating a repo, adding or changing a LICENSE, setting a license field in package metadata, or answering "what license should this be". Pick the tier from intent, then act.
kai-tech-prefs - other repo conventions.