ci-server-engineer/.claude/skills
cliu 1c3558c37c Complete phase 1 and build the CI-Eng-Sample project
Add verified system-management tasks (item read/write, quick load
records, history load, monitoring processes, consistency check, tuning
checks), the importable CI-Eng-Sample project with load/remove scripts,
the unlicensed 1-hour shutdown note, and the sample-project re-test
rule. Close ISS-002/003/004 and log ISS-005..007.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-30 14:01:33 +10:00
..
system-check Complete phase 1 and build the CI-Eng-Sample project 2026-09-30 14:01:33 +10:00
system-management Complete phase 1 and build the CI-Eng-Sample project 2026-09-30 14:01:33 +10:00
README.md Add phase 0-1 knowledge and system skills 2026-09-30 13:07:37 +10:00

Skills

One skill per CI Server area, following knowledge/document-map.md. Nested skill folders are not used for grouping; group tasks inside each skill instead:

<area>/
├── SKILL.md       # frontmatter (name, description with task keywords) + task index
├── tasks/         # one file per task
└── reference/     # area-specific details

The description in SKILL.md decides when Claude uses the skill. List the words users will actually say.

Skills must work on any R1.03 system, so never use names from a particular system (items, sections, stations, nodes). Write placeholders such as <Section>.<Tag> and, where an example helps, use names from the sample project CI-Eng-Sample (examples/CI-Eng-Sample/). Test-system evidence belongs in knowledge/progress.md and knowledge/issues.md.