CtrlK
BlogDocsLog inGet started
Tessl Logo

codex-thread-heartbeat

Inspect and manage guarded Codex App-native or launchd heartbeats for Codex main control threads. Use when the user wants Codex to periodically continue a specific thread only when it is idle, avoid interrupting active work, keep App-visible interactions, inspect thread status, or enable/disable project autopilot heartbeats.

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured with executable commands, a clear ordered transport-selection workflow, and explicit validation/safety checkpoints. The main weakness is mild repetition of the App-visibility caveat across multiple sections, which slightly reduces token efficiency.

Suggestions

Consolidate the App-visibility limitation into a single section (e.g., Transport Choice or Safety Rules) instead of restating it in the intro, the launchd fallback note, and the safety rules.

Add a short example of an actual bounded heartbeat prompt payload so the "ask for one small verifiable step" guidance is concrete rather than only descriptive.

Consider a one-line reference pointer to the script's own help output (e.g., `codex-thread-queue.py --help`) for full command discovery instead of listing every subcommand inline.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence (no explaining what a heartbeat is), but the App-vs-headless visibility caveat ("the currently open Codex App view may not refresh") is restated across the intro, transport choice, and safety rules, so it could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready commands such as `... codex-thread-queue.py heartbeat-presets`, `install-preset agent-harness`, `heartbeat-enable`, and a `--title ... --cwd ... status` invocation rather than pseudocode.

3 / 3

Workflow Clarity

The Transport Choice section gives a clear ordered decision sequence (1, 2, 3) and the Safety Rules include explicit validation checkpoints such as "Prefer status or dry-run heartbeat before enabling" and "Do not use direct codex exec resume automation without idle checks".

3 / 3

Progressive Disclosure

Content is self-contained and well-organized into clear sections (Transport Choice, Quick Commands, Safety Rules, Open Source Positioning) with a one-level reference to the bundled script at scripts/codex-thread-queue.py, which exists on disk; no nested references.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, third-person, and clearly separates what the skill does from when to use it via an explicit "Use when" clause. It lists several concrete actions and natural trigger terms with minimal fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in third person voice — "Inspect and manage guarded Codex App-native or launchd heartbeats", "inspect thread status", "enable/disable project autopilot heartbeats" — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ("Inspect and manage guarded Codex App-native or launchd heartbeats...") and when via a clear "Use when the user wants..." clause enumerating trigger conditions.

3 / 3

Trigger Term Quality

Covers natural intent phrasings a user would say ("periodically continue a specific thread only when it is idle", "avoid interrupting active work", "keep App-visible interactions", "enable/disable project autopilot heartbeats"), not just technical jargon.

3 / 3

Distinctiveness Conflict Risk

Targets a very specific niche (guarded Codex thread heartbeats with idle guards) with distinct triggers unlikely to overlap with other skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
huangruiteng/CS-Notes
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.