Sentience capture status — is the Claude Code hook wired and capturing governance events? Quick health check.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add crescerelabs/sentience-governor --skill sentience-status --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Sentience Status?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/crescerelabs-sentience-status)More formats (shields.io, HTML) on the badges page.
---
name: sentience-status
description: |
Sentience capture status — is the Claude Code hook wired and
capturing governance events? Quick health check.
disable-model-invocation: true
allowed-tools: Bash(sentience status *)
---
!`sentience status`
Render the command output above verbatim in a code block. Do not
summarize, reinterpret, reformat, read trace files, or compute
substitute results. If the output says no_signal, no_turns, or
no_token_data, show it as-is and stop. Do not use Sentience report
headings unless they appear in the command output. Add no prose of
your own after the code block. If the user explicitly asks you to
explain it, reply starting with
`Interpretation (not Sentience output):` and use only the rendered
report.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!