Install
$ agentstack add skill-jiplet-transformation-os-clevel-review ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
/clevel-review
Pre-output gate. Three phases. Hard enforcement: do NOT skip to Phase 3.
Canonical spec: /6 - slash commands/clevel-review.md
Phase 1: Classify and self-validate the council
Required inputs
Ask the user (via AskUserQuestion if any are missing):
- Deliverable type — decision brief / status / risk / category strategy / contract change / conversation prep / one-pager / steerco pack / external client doc
- Audience — named person + role (e.g. "Group GM Supply Chain"; "CFO"; "client contact at a government department")
- Format — 1-page Obsidian markdown / Word docx / PPTX deck / dashboard / email
- Ask type — support / approval / information / decision / endorsement
- Source material — brief, draft, wiki path, prior outputs (if any)
Routing
- Read
/CLAUDE.md"Orchestrator, Routing Logic" section (lines covering thinker triggers). - Match the inputs above to thinker triggers. Multi-signal tasks load multiple thinkers.
- Read each matched thinker file from
/context/.md.
Mandatory thinker triggers (not exhaustive, see CLAUDE.md routing table for full):
| Signal | Thinker file(s) | |---|---| | Initiative sizing / "should we do this" | cso.md | | Financial claim / one-pager / CFO summary | cfo.md | | Named client (a state-government facilities client, a telco client, Defence, a national network client, state transport) | chief-client-officer.md + general-counsel.md | | Category, vendor, panel, supplier consolidation | cpo.md + coo.md | | System / data / Databricks / SAP dependency | cio.md + data-landscape.md | | Contract terms, EA, legal feasibility | general-counsel.md + cro.md | | Workforce, leave, restructure | chief-people-officer.md + general-counsel.md | | Risk, insurance, WHS, regulatory | cro.md | | Operational feasibility, change management | coo.md + delivery-difficulties.md | | Cost modelling, inflation, market rates | chief-economist.md | | Visual deliverable (deck, dashboard, web) | cdo.md | | Steerco / ExCo update | cso.md + cfo.md |
Phase 1 output (write to user)
## Classification
| Field | Value |
|---|---|
| Deliverable type | … |
| Audience | … |
| Format | … |
| Ask type | … |
## Council loaded
| Thinker | Why loaded | File read |
|---|---|---|
| … | … | ✓ |
Stop. Ask user to confirm before Phase 2: "Council looks right? Add or remove any thinker before I run critique."
Phase 2: Council critique
For each loaded thinker, produce critique IN THAT THINKER'S VOICE using:
- The thinker's "Questions This Thinker Always Asks" (apply to the draft / proposal)
- The thinker's "Anti-Patterns This Thinker Catches" (red-flag scan)
- The thinker's "Company Context" (relevance check)
Output format
## Council critique
### [Role] (file: [thinker].md)
**Voice:** [1-2 sentences framing what this thinker brings]
**Challenges raised:**
- [Specific challenge tied to the draft / proposal]
- …
**Anti-patterns flagged:**
- [Specific pattern in the draft this thinker catches]
**Yes if:**
- [What would need to change for this thinker to support]
---
[Repeat per thinker]
## Consolidated MECE issues
| # | Issue | Raised by | Severity | Resolution |
|---|---|---|---|---|
| 1 | … | … | high/med/low | … |
Stop. Ask user to confirm or push back on any critique before Phase 3.
Phase 3: Audience-shaped write-up
Format selected from classification, NOT from topic.
Format library (v1)
| Audience | Format | Skill to call | |---|---|---| | GM / Sector exec | 1-page Obsidian markdown | (this skill, GM template below) | | CFO | 1-page markdown + optional Word | program-exec-summary | | ExCo / Steerco | PPTX | program-steerco-pack | | External client | Word doc | analysis-commercial-insight |
v1 ships GM-only. For CFO / ExCo / External, run Phase 1 + 2 then hand off to the named skill with the consolidated issue list.
Auto-chain: after Phase 3 produces the draft, automatically invoke /exec-comms to apply visual + structural format discipline (callouts, parallel tables, bold-the-punchline, banned-word scan, length cap to audience tier). The chain is mandatory, not optional. /exec-comms enforces the format rules; /clevel-review produces the content.
GM 1-page template (mandatory structure)
# [Title]
> Audience: [named person] | Read time: [N] min | Date: [YYYY-MM-DD]
## Decision sought
[1 sentence. The single thing this page asks for.]
## Situation
- [3-4 MECE bullets. Where we are.]
## Complication
- [3-4 MECE bullets. Why current state cannot deliver alone.]
## Asks (parallel)
| # | Ask | Who carries if approved | Effort | Outcome |
|---|---|---|---|---|
## What we commit in return
- [3 bullets. Reciprocal commitment.]
## What's at stake by [date]
- [2 bullets. Cost of inaction, anchored to a real deadline.]
## Appendix
[Links only. No narrative.]
Banned patterns (refuse to ship if any present)
- "What this is NOT" sections (defensive, undermines confidence)
- "Pre-empted Questions" sections (if asked, answer; don't pre-litigate)
- Mixed tactical / structural detail in same section (force separate buckets)
- Asks of different shapes (parallel structure mandatory)
- Value tables before the ask (lead with the answer, not the proof)
- Headlines without urgency markers (anchor to deadline)
Safety / failure modes
- Thinker file missing: warn, list missing thinker, proceed with degraded council, flag in output.
- User wants to skip Phase 2: warn that this defeats the gate; require explicit
--skip-critiqueflag from user; log the skip in the output deliverable. - Audience unknown: ASK via AskUserQuestion. Do not guess.
- Multiple audiences: default to most senior; flag secondary as constraint.
- Conflict between thinkers: surface to user as decision point. Do not auto-resolve.
Logging
Optional. If user passes --log , write the Phase 1 + 2 outputs as a markdown file at that path alongside the deliverable. Default: no log.
Reference
- Spec:
/6 - slash commands/clevel-review.md - Routing logic:
/CLAUDE.md(Orchestrator section) - Thinker files:
/context/*.md - Output skills:
program-exec-summary,program-steerco-pack,analysis-commercial-insight
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Jiplet
- Source: Jiplet/transformation-os
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.