ci-server-engineer/.claude/skills
cliu ef543cde20 Add phase 5 Engineering Module summary, authorization skill, item tests
- Summary of IM 36K10C10 (Engineering Module - I/O Processes), checked
  against dssana.sup, itm.sup and the default datasets
- New skill authorization: users and authorization groups by quick load
- item-engineering: string item limits (1-200, holds length - 1) and the
  integration granule (itm_int_secs), both tested on CI-Eng-Sample
- CI-Eng-Sample: read-only authorization group CIENG_VIEWER
- Closed ISS-001 (uoff/ublk option bits), ISS-010, ISS-019; new ISS-018, ISS-020

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-30 17:09:45 +10:00
..
authorization Add phase 5 Engineering Module summary, authorization skill, item tests 2026-09-30 17:09:45 +10:00
class-object-engineering Record confirmed tutorial tasks in item and class/object skills 2026-09-30 15:56:49 +10:00
installation-security Add phase 3 Tutorial summary and extend CI-Eng-Sample 2026-09-30 15:45:43 +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 Complete phase 1 and build the CI-Eng-Sample project 2026-09-30 14:01:33 +10:00
system-management Add phase 5 Engineering Module summary, authorization skill, item tests 2026-09-30 17:09:45 +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.