Skip to content
Back to skills

Create Status Surface

ASecurity

Create receipt-backed status surfaces and Tau DAG handoff contracts from local progress, gate, and checker receipts. Use when a workflow needs a global progress bar, evidence status board, local readiness surface, or robust Tau connection without claiming provider readiness or live completion.

  • 6 stars
  • 0 votes
  • 0 copies
  • 5 views
  • Added September 11, 2026
businesspythongobashnodegit

Works with

  • terminal

Security analysis

A100/100

Pro scans all 10 files and shows the line behind each finding

Scanned September 11, 2026

npx -y skills add grahama1970/agent-skills --skill create-status-surface --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Create Status Surface?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Create Status Surface
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/grahama1970-create-status-surface/badge)](https://www.skillsdirectory.com/skills/grahama1970-create-status-surface)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: create-status-surface
description: >
  Create receipt-backed status surfaces and Tau DAG handoff contracts from local
  progress, gate, and checker receipts. Use when a workflow needs a global
  progress bar, evidence status board, local readiness surface, or robust Tau
  connection without claiming provider readiness or live completion.
triggers:
  - create status surface
  - status surface
  - global progress bar
  - receipt-backed progress
  - render progress receipt
  - tau status handoff
  - tau dag status surface
provides:
  - status-surface
  - receipt-backed-progress
  - tau-dag-status-contract
  - progress-tracking
composes:
  - tau
  - agentic-evals
complies:
  - best-practices-skills
  - best-practices-python
runtime_self_improvement: basic
taxonomy:
  - validation
  - orchestration
  - progress-tracking
  - evidence
disciplines:
  - observability-operations
  - agentic-orchestration
---

# Create Status Surface

Build local, receipt-backed status surfaces from machine-readable progress
artifacts. The skill is reusable across pipelines because it treats receipts as
source truth and renders derived surfaces only.

Default input:

```text
persona_dream.global_progress.v1
```

Outputs:

```text
status_surface.json
status_surface.html
status_surface_receipt.json
tau_status_surface_dag_contract.v1.json
tau_status_surface_dag_validation_receipt.json
```

## Hard Boundary

This skill never upgrades a local progress rollup into:

```text
provider readiness
manual acceptance
paid-call authorization
live provider submission
live Tau DAG execution
visual quality acceptance
```

It may create a Tau DAG contract for inspection or local orchestration handoff,
but that contract is not a Tau execution receipt.

## Commands

```bash
skills/create-status-surface/run.sh render \
  --input /path/to/global_progress.v1.json \
  --output-dir /tmp/status-surface \
  --title "Persona Dream"

skills/create-status-surface/run.sh validate \
  --surface /tmp/status-surface/status_surface.json \
  --receipt-out /tmp/status-surface/status_surface_validation_receipt.json

skills/create-status-surface/run.sh tau-dag \
  --surface-receipt /tmp/status-surface/status_surface_receipt.json \
  --output /tmp/status-surface/tau_status_surface_dag_contract.v1.json

skills/create-status-surface/run.sh tau-check \
  --dag /tmp/status-surface/tau_status_surface_dag_contract.v1.json \
  --receipt-out /tmp/status-surface/tau_status_surface_dag_validation_receipt.json

skills/create-status-surface/run.sh tau-doctor \
  --receipt-out /tmp/status-surface/tau_doctor_receipt.json
```

Run local sanity:

```bash
skills/create-status-surface/sanity.sh
```

## Tau Connection Rules

- Use `skills/tau/run.sh doctor` for non-mutating Tau wrapper connectivity.
- Generate `tau.dag_contract.v1` with explicit `goal_hash`, nodes, edges,
  terminal human node, limits, required evidence, and fail-closed invariants.
- Use `executor: local` for local status-surface commands and `executor: human`
  for the terminal boundary.
- Do not use `executor: provider`.
- Do not claim Tau execution unless a separate Tau DAG receipt exists.
- Do not create GitHub, provider, Herdr, or browser mutation claims from this
  skill.

## Proof Standard

For reports, include:

```text
mocked: no
live: no for local fixture rendering
actual_provider_call_attempts: 0
live_tau_dag_execution_started: false
```

`tau-doctor` is live only in the narrow sense that it invokes the local Tau
wrapper; it is still non-mutating and does not prove provider execution.

Files in this skill

  • .gitignore35 B
  • SKILL.md3.5 KB
  • agents/openai.yaml278 B
  • fixtures/agentic_eval.json499 B
  • fixtures/persona_dream_global_progress.v1.json2.1 KB
  • pyproject.toml161 B
  • run.sh387 B
  • sanity.sh1.8 KB
  • scripts/create_status_surface.py23.9 KB
  • uv.lock6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.