cedarwud/beamho-traceability-profile-edit
agent-skills/beamho-traceability-profile-edit/SKILL.md
Use when editing beamHO-bench paper profiles, source maps, assumption-backed research parameters, or paper-source registries so schema, profile JSON, sources JSON, and validation coverage stay traceable and synchronized.
data-ai
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add cedarwud/beamHO-bench beamho-traceability-profile-editInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 1:58 AM12.2s1 file scanned
SKILL.md
- name:
- beamho-traceability-profile-edit
- description:
- Use when editing beamHO-bench paper profiles, source maps, assumption-backed research parameters, or paper-source registries so schema, profile JSON, sources JSON, and validation coverage stay traceable and synchronized.
beamHO Traceability And Profile Edit
Use this skill for beamHO-bench/ when the task changes profile values, adds a new research parameter, edits ASSUME-* entries, or touches source-trace mappings.
Read First
Read these first:
AGENTS.mdPROJECT_CONSTRAINTS.mdsrc/config/paper-profiles/paper-profile.schema.json- the target profile JSON and matching
.sources.json src/config/references/paper-sources.json- if research-parameter UI/runtime is affected:
src/config/research-parameters/catalog.tssrc/config/research-parameters/consistency.ts
- if lifecycle or closure state changes:
sdd/completed/beamHO-bench-implementation-status.mdsdd/pending/README.md
Primary Edit Surfaces
These files usually move together:
src/config/paper-profiles/<profile>.jsonsrc/config/paper-profiles/<profile>.sources.jsonsrc/config/references/paper-sources.jsonsrc/config/paper-profiles/paper-profile.schema.jsonsrc/config/research-parameters/catalog.tssrc/config/research-parameters/consistency.ts
Do not change only one of these when the data contract clearly spans more than one surface.
Traceability Rules
- Every new
sourceIdreferenced by a profile, parameter catalog entry, or source map must exist insrc/config/references/paper-sources.json. - Every new
ASSUME-*must:- be added to
paper-sources.json - have a clear locator / note
- be used only where the project intentionally falls back to an assumption
- be added to
- If a profile field value changes and its justification changes, update the matching
.sources.json. - If a new profile field is introduced:
- update
paper-profile.schema.json - update any affected types / loader logic if needed
- update matching
.sources.jsonentries
- update
- If a research-parameter option changes runtime behavior:
- keep
catalog.tsandconsistency.tsaligned - do not leave hidden coupling undocumented
- keep
Change Workflow
- Start from the target profile or source-trace path.
- Identify whether the change is:
- value-only
- new traceability source
- new schema field
- new research parameter or coupling rule
- Apply the smallest synchronized change set across all impacted files.
- Check for missing
sourceIds, stale.sources.jsonpaths, or schema drift before validating.
Validation
These changes are stage-gate-sensitive. Prefer running:
npm run lintnpm run test:simnpm run buildnpm run validate:stage
At minimum, do not skip stage validation when changing:
- profile JSON structure or values
- source maps
paper-sources.jsoncatalog.tsconsistency.ts
Reporting
Always report:
- which profile or traceability surfaces changed
- whether a new
ASSUME-*orsourceIdwas introduced - what schema or consistency rules changed
- what validation ran
Related Skills
cedarwud/beamho-validation-closure
testing
VerifiedTrustedCommunity
Use when validating beamHO-bench changes, deciding which project gates to run, preparing SDD closure, or checking whether lifecycle docs and manual acceptance evidence are sufficient before marking work complete.
SKILL.mdUpdated Apr 16, 2026
cedarwud/beamho-sdd-workflow
development
VerifiedTrustedCommunity
Use when developing, reviewing, or closing work in beamHO-bench that is governed by an active pending SDD, especially when the task requires reading PROJECT_CONSTRAINTS, active pending status, validation rules, and lifecycle-sync docs before editing code.
SKILL.mdUpdated Apr 16, 2026
cedarwud/beamho-observer-sky-frontend
development
VerifiedTrustedCommunity
Use when editing beamHO-bench observer-sky satellite rendering, composition, camera framing, display selection, continuity, or screen-space acceptance so frontend changes stay aligned with visual-acceptance rules instead of proxy metrics alone.
SKILL.mdUpdated Apr 16, 2026
openclaw/taskflow-inbox-triage
data-ai
VerifiedTrustedCommunity
Example TaskFlow authoring pattern for inbox triage. Use when messages need different treatment based on intent, with some routes notifying immediately, some waiting on outside answers, and others rolling into a later summary.
357,764SKILL.mdUpdated Apr 10, 2026