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.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/codex-thread-heartbeat/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

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

The body is actionable and well-structured with a real bundled script and concrete commands. It is held back by padded explanatory prose and the absence of an explicit validation feedback loop for its batch heartbeat operations.

Suggestions

Trim the 'pain it solves' bullets, the app-server transport rationale, and the 'Open Source Positioning' section to the essentials to improve conciseness.

Add an explicit validate->fix->retry feedback loop for the heartbeat enable/verify cycle (e.g., run heartbeat-status, confirm idle-guard passed, then enable, then re-check status) so the batch workflow earns a higher workflow-clarity score.

Replace the repeated absolute paths (~/.codex/skills/codex-thread-heartbeat/scripts/codex-thread-queue.py) with a short variable or alias defined once at the top of the Quick Commands section.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of basic-concept padding, but the 'pain it solves' prose, the app-server transport rationale, and the 'Open Source Positioning' section are explanatory padding that could be tightened.	3 / 5
Actionability	Provides concrete, copy-pasteable commands for the real bundled script (heartbeat-presets, install-preset, heartbeat-enable/disable/status, a full --title/--cwd status example), with only minor gaps such as no inline example of the heartbeat prompt content.	4 / 5
Workflow Clarity	A clear transport-preference order and a safety checklist exist, but this is a batch/automated (launchd) operation and the body lacks an explicit validate->fix->retry feedback loop, so workflow clarity is capped at 3 per the batch-operation rule.	3 / 5
Progressive Disclosure	Well-organized into clear sections with a single one-level-deep reference to the real scripts/codex-thread-queue.py bundle file; minor verbosity in the repeated absolute command paths keeps it from a 5.	4 / 5
	Total	14 / 20 Passed

Description

87%Weight 40%Scale 1-5

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 strong: it clearly states the skill's purpose, provides a rich 'Use when' trigger clause, and occupies a distinct niche. It is only slightly held back on specificity and trigger-term breadth.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Inspect and manage', 'periodically continue a specific thread only when it is idle', 'enable/disable project autopilot heartbeats') with only minor gaps in coverage.	4 / 5
Completeness	Explicitly answers both what (inspect and manage guarded heartbeats) and when, with a concrete 'Use when the user wants ...' clause enumerating multiple trigger scenarios.	5 / 5
Trigger Term Quality	Good coverage of natural user phrasings ('periodically continue a specific thread', 'when it is idle', 'inspect thread status', 'enable/disable ... heartbeats'), though a few common synonyms (e.g. 'keep alive', 'nudge', 'loop') are missing.	4 / 5
Distinctiveness Conflict Risk	The niche is highly specific ('guarded Codex App-native or launchd heartbeats for Codex main control threads') with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: huangruiteng/CS-Notes
Path: .codex/skills/codex-thread-heartbeat/SKILL.md
Commit: a7d9500

Reviewed: 7 hours ago

Table of Contents

Discovery Implementation Validation

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.