status
/status
Pokazuje migawkę aktywnej pracy agentów, dostarczania w Git, tożsamości wykonania i limitów zużycia, także przy zablokowanych zadaniach.
- Autor
- shenxingy ↗
- Repozytorium
- clade ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 24.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 5
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 24.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Pokazuje migawkę aktywnej pracy agentów, dostarczania w Git, tożsamości wykonania i limitów zużycia, także przy zablokowanych zadaniach.
Wyzwalacze z opisu
Oryginalny opis (EN)
Show a provider-neutral, freshness-aware snapshot of active Agent work, Git delivery, execution identity, and usage limits. Use for “what's going on right now”, what is running, progress updates, active runtime/provider/model, or stuck-work checks.
Jak działa
- Canonical Clade workflow
- Required semantic fields
- Collection order
- Output
- Completion
- Codex surface adapter
- Additional skill reference
- Delivery completion
Podgląd SKILL.md
---
name: status
description: "Show a provider-neutral, freshness-aware snapshot of active Agent work, Git delivery, execution identity, and usage limits. Use for “what's going on right now”, what is running, progress updates, active runtime/provider/model, or stuck-work checks."
---
# Clade for Codex
This package composes the provider-neutral Clade core contract with the native
Codex surface adapter. Run the workflow directly in Codex; do not launch
another agent CLI or route it through Clade MCP.
Package provenance:
- core contract: `clade.status/v1`
- surface adapter: `codex/v1`
- explicit invocation: `$clade:status`
- generated from: `configs/skills/<name>`
## Canonical Clade workflow
<command-metadata>
name: status
contract: clade.status/v1
completion-status: DONE | DONE_WITH_CONCERNS | BLOCKED
</command-metadata>
Build one compact status snapshot from sources available on the current
surface. Keep collection read-only.
## Required semantic fields
- `observed_at`
- task identity/state and progress `{completed,total,source}`
- Git branch, dirty state, checkpoint SHA, upstream divergence
- execution runtime, connection, inference provider, wire model, degradations
- usage/rate-limit observations with source and observed/reset timestamps
- freshness per source
Unknown is a first-class value:
- Never render missing progress or quota data as `0`, `0%`, unlimited, or done.
- Never infer a provider from a model prefix or a model from the runtime name.
- Mark estimates explicitly and show the evidence behind them.
- Distinguish stale data, unreachable sources, unsupported capabilities, and
authoritative zero values.
## Collection order
1. Read conversation/runtime activity exposed by this surface.
2. Inspect local Git without mutation. Prefer the delivery controller's
`git_context.py` when installed; otherwise use read-only Git commands.
When the Git-common `clade/tasks/binding.json` exists, resolve the installed
tasks skill directory as TASKS_ROOT and run
`python3 "$TASKS_ROOT/scripts/maintenance.py" status` first. This reads
maintenance observations without requiring the database, and reports stale
health, missing/failed backups and restore verification. Treat an unmanaged
or unsupported service as unknown, not healthy. Then run
`python3 "$TASKS_ROOT/scripts/tasks.py" snapshot`. Use its project/task/
session IDs, ownership, ready set and submission evidence. An unavailable
backend is unavailable, not zero tasks. Do not run claim or heartbeat here.
3. Read Clade worker `status_snapshot` / `execution_envelope` if an
orchestrator is reachable.
4. Query forge/CI only when a related PR is in scope.
5. Query native usage data only through the current surface adapter.
## Output
Keep the human view under 20 lines unless the user asks for JSON. Show:
```text
Work: state · factual progress or unknown · freshness
Git: branch · dirty/clean/unknown · checkpoint/upstream
Execution: runtime · connection · inference provider · wire model
Limits: authoritative windows, or unknown/unavailable with reason
Delivery: PR/checks/merge state when in scope
Concern: stale/hung/degraded evidence, if any
Next: one concrete recommendation
```
Call work “hung” only when a source provides timestamps and no relevant change
has occurred past the repository/runtime threshold. Do not kill, restart,
commit, push, or merge from this read-only skill.
## Completion
- `DONE`: snapshot is clear and all relevant sources were observed.
- `DONE_WITH_CONCERNS`: one or more sources are stale, unavailable, or
degraded; name them.
- `BLOCKED`: even local/runtime state cannot be read; show the exact failure.
## Codex surface adapter
# Codex status adapter
- Invoke the installed plugin workflow explicitly as `$clade:status`; bare
`$status` is not the Clade plugin identity.
- Use Codex task/tool activity exposed in the current conversation.
- Codex TUI status-line configuration is an ordered list of native fields, not
an arbitrary command renderer. Do not claim Claude-style custom rendering.
- Use `$clade:codex-usage --json` when installed for authenticated native limit
observations; otherwise report limits as unavailable/unknown.
- Read the applicable agent instructions before interpreting
repository-specific progress. `AGENTS.override.md` wins over `AGENTS.md` at
each scope with no merge, so do not report a shadowed `AGENTS.md` as in
effect; trusted legacy `CLAUDE.md` is Clade's own fallback rather than a
filename Codex resolves.
- Do not launch a nested Codex CLI to discover status.
## Additional skill reference
# Status
Render one `clade.status/v1` snapshot. Separate observed facts from estimates,
attach source/freshness, and preserve unknown values as unknown. Read
`prompt.md` for the core contract and only the current runtime file under
`surfaces/` for collection mechanics.
## Delivery completion
If this workflow changes files or external state:
- Inspect the real final state before responding, including `git status` for a
repository task.
- Never report `DONE` while task-owned changes are uncommitted. Use or continue
`$clade:delivery` and create a repository-compliant checkpoint or preserve
the work when committing is unavailable.
- When the user request or trusted repository policy makes publication,
deployment, or live verification part of the task, do not silently downgrade
the result to local-only work.
- If a required delivery transition lacks authority, credentials, a destination,
or reachable external state, report `BLOCKED` or `NEEDS_CONTEXT` rather than
appending a "not committed/pushed/deployed" caveat after `DONE`.
Pliki w paczce (5)
- SKILL.md 6 KB
- surfaces/claude-code.md 1 KB
- surfaces/codex.md 1 KB
- surfaces/generic.md 1 KB
- surfaces/mcp.md 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · shenxingy/clade | 100 | MIT |
| finolabs/finolabs-vibecode | 100 | MIT |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| rossoctl/context-guru | 100 | Apache-2.0 |
| crisandrews/clawcode | 100 | MIT |
| wrg32786/aigent-os | 100 | MIT |
| zereight/gitlab-mcp | 100 | MIT |
| emaballarin/ccplugins | 100 | MIT |
| wookiya1364/scv-claude-code | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 3e580c5e251b (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 95ar-status
Pokazuje panel eksperymentu autoresearch z wynikami, aktywnymi pętlami i postępem, po poleceniu /ar:ar-status. - 90live
Pokazuje stan uruchomionych sesji i agentów, czyli co działa i co wymaga uwagi, gdy użytkownik pyta o ich status. - 90ralph-specum-status
Pokazuje stan aktywnej specyfikacji w Ralph Specum i postęp prac, na wyraźne żądanie. - 100use-claude-limits-efficiently
Pilnuje limitów 5-godzinnych i tygodniowych przy długiej lub równoległej pracy agentów: sprawdza zużycie między falami i wznawia po odnowieniu okna. - 100usage-bridge
Instaluje, usuwa albo sprawdza mostek statusu limitów w galdr, który pokazuje procent zużycia i wstrzymuje pracę na limicie. - 100bernstein-status
Pokazuje stan orkiestratora Bernstein: aktywnych agentów, postęp zadań, koszty i alerty.