ci-server-engineer/.claude/skills
cliu 5c0126d757 Close ISS-008, ISS-031, ISS-032, ISS-034
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-01 11:01:07 +10:00
..
authorization Add phase 5 Engineering Module summary, authorization skill, item tests 2026-09-30 17:09:45 +10:00
class-object-engineering Extend class-object-engineering skill: language, Java, reset, opcdbg tasks 2026-09-30 17:49:49 +10:00
data-access Add data-access skill, BUS utilities task and licence run-time notes 2026-10-01 10:46:28 +10:00
equipment Add data-access skill, BUS utilities task and licence run-time notes 2026-10-01 10:46:28 +10:00
installation-security Close ISS-008, ISS-031, ISS-032, ISS-034 2026-10-01 11:01:07 +10:00
item-engineering Add phase 5 Engineering Module summary, authorization skill, item tests 2026-09-30 17:09:45 +10:00
portal-setup Add phase 4 CI Portal setup and Setup File Editor summaries, portal-setup skill 2026-09-30 16:41:02 +10:00
system-check Add data-access skill, BUS utilities task and licence run-time notes 2026-10-01 10:46:28 +10:00
system-management Add data-access skill, BUS utilities task and licence run-time notes 2026-10-01 10:46:28 +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.