fix(skills): add YAML frontmatter to telos-load + regulatory-risk-assessment
release / tag (push) Successful in 1s

The two new skills shipped without the name/description frontmatter every
other skill carries, so harnesses surfaced them as a bare directory name
with no description to match against intent. Add frontmatter (body unchanged).

Bump-Type: patch

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-06-18 18:19:19 +02:00
co-authored by Claude Opus 4.8
parent b7d8cfc3cc
commit 8f14c572b9
2 changed files with 10 additions and 0 deletions
+5
View File
@@ -1,3 +1,8 @@
---
name: regulatory-risk-assessment
description: Produce a structured regulatory risk assessment / risk-register entry for regulated-industry features (banking, payments, PSD2/PSR, DORA, AML). Use when filing a CAD issue that needs a Risk:LOW/MEDIUM/HIGH level, or designing features touching payments, auth, data storage, or external APIs ("what are the risks?", "compliance gate", "risk register").
---
# regulatory-risk-assessment
Produce a structured regulatory risk assessment for a feature, component,
+5
View File
@@ -1,3 +1,8 @@
---
name: telos-load
description: Load TELOS — the intention substrate (problems, goals, strategies, status) — into a session at start so every decision traces to a goal. Use when starting any koala session, before architectural decisions, or as the CAD pipeline entry point ("load TELOS", "what are we optimizing toward?").
---
# telos-load
Load TELOS — the intention substrate — into a session so every decision