skill-library-maintainer

スター2

フォーク0

更新日2026年4月2日 03:32

Use when adding, removing, renaming, reorganizing, or documenting large skill knowledge bases or template libraries in this repository, especially nixos-knowledge-base and nixos-patterns.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

luo216

luo216/NixOS-Agent

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Skill Library Maintainer

Use this skill only for large skill assets such as knowledge bases and template libraries.

Normal small skills do not need this level of process.

Scope

backend/config/skills/nixos-knowledge-base/
backend/config/skills/nixos-patterns/
future large local knowledge or template libraries with many files

File Tree

.
`-- SKILL.md

Rules

Prefer improving navigation before reshaping content.
For knowledge bases, keep mirrored source content stable; add or refine SKILL.md, README.md, MAP.md, and INDEX.md style navigation around it.
For template libraries, keep entry paths shallow and easy to scan.
For template libraries, each template README should expose a short File Tree or High-Level Tree so planner can skim structure before reading the full content.
Distinguish starter templates from reference repos in the docs even if they share one flat directory.
When adding a new large branch, update the nearest navigation document in the same change.
Do not dump huge full trees into SKILL.md; use a high-signal tree and expose the most common second-level entry points only.
Do not dump huge full trees into template README files either; use one screen of high-signal structure that helps early template selection.
If names are ambiguous, rename toward searchable repo-like or purpose-like names.
If planner or other roles depend on the old path or naming, update those references in the same change.

Typical Checklist

Is the entry path easy to guess?
Can a first-time reader tell where to start?
Can planner understand the template shape from one short structure tree?
Does the docs layer explain starter vs reference, light vs heavy, practical vs authoritative?
Did any existing skill manual or README keep an outdated path?
Did you append codex-progress.md and create a git commit?

このリポジトリの他の Skills

同じリポジトリ

codex-operations-manual

luo216/NixOS-Agent

Entry skill for `.codex` collaboration. Read the role-specific manual for your current client.

2026-05-162

nixos-patterns

luo216/NixOS-Agent

Reusable NixOS, Home Manager, and flake configuration patterns. Use when planner or implementer needs proven directory structures, module split patterns, host layouts, secrets organization, overlays, or template-style examples instead of abstract explanation.

2026-04-262

nixos-knowledge-base

luo216/NixOS-Agent

Use this skill when the user asks for Nix, Nixpkgs, or NixOS knowledge from local documentation mirrors in this workspace. Start with the high-priority flakes-book branch for practical NixOS and Flakes workflows, then fall back to the official manuals, the NixOS options/module corpus, and the small supplemental wiki navigation branch.

2026-04-022

nixos

luo216/NixOS-Agent

NixOS and Nix flake development for multi-repo architectures, airgapped deployments, and K3s infrastructure. Use when working with flake.nix files, NixOS modules, derivations, devShells, overlays, OCI image packaging, or composing multiple flake repositories. Covers Nix language syntax, flake inputs/outputs, nixosModules exports, stdenv.mkDerivation, and home-manager integration.

2026-04-022

nixpkgs-inspector

luo216/NixOS-Agent

Verify whether a NixOS option, Home Manager option, nixpkgs package, module, or attr path actually exists. Use local nix commands and ripgrep instead of guessing.

2026-04-022

tmux-session-runner

luo216/NixOS-Agent

Minimal tmux runner for one task per session. Use when Codex needs to create an isolated tmux session, send commands into that session's main shell, inspect the session status, or inspect recent output from the main window.

2026-04-022

Skill Library Maintainer

Use this skill only for large skill assets such as knowledge bases and template libraries.

Normal small skills do not need this level of process.

Scope

backend/config/skills/nixos-knowledge-base/

backend/config/skills/nixos-patterns/

future large local knowledge or template libraries with many files

File Tree

. `-- SKILL.md

Rules

Prefer improving navigation before reshaping content.

For knowledge bases, keep mirrored source content stable; add or refine SKILL.md, README.md, MAP.md, and INDEX.md style navigation around it.

For template libraries, keep entry paths shallow and easy to scan.

For template libraries, each template README should expose a short File Tree or High-Level Tree so planner can skim structure before reading the full content.

Distinguish starter templates from reference repos in the docs even if they share one flat directory.

When adding a new large branch, update the nearest navigation document in the same change.

Do not dump huge full trees into SKILL.md; use a high-signal tree and expose the most common second-level entry points only.

Do not dump huge full trees into template README files either; use one screen of high-signal structure that helps early template selection.

If names are ambiguous, rename toward searchable repo-like or purpose-like names.

If planner or other roles depend on the old path or naming, update those references in the same change.

Typical Checklist

Is the entry path easy to guess?

Can a first-time reader tell where to start?

Can planner understand the template shape from one short structure tree?

Does the docs layer explain starter vs reference, light vs heavy, practical vs authoritative?

Did any existing skill manual or README keep an outdated path?

Did you append codex-progress.md and create a git commit?

name	skill-library-maintainer
description	Use when adding, removing, renaming, reorganizing, or documenting large skill knowledge bases or template libraries in this repository, especially nixos-knowledge-base and nixos-patterns.