he-phase-heartbeat

Routes old phase-heartbeat requests into HE phase work: check the approved plan, reuse or create a 10-minute continuation only with authority, run phase gates, delegate the active slice to he-work, and stop before commit or tracker closure. Use when a user says phase heartbeat, keep this PR moving, or continue phases.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

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 a well-structured, actionable orchestration skill with clear sequencing, validation gates, and a concrete output template. Its only real weakness is repeated stop/authority language across sections that inflates token cost without adding clarity.

Suggestions

Consolidate the recurring 'stop before staging/commit/merge/review-thread/Linear/deploy/destructive cleanup' list into a single canonical statement and reference it, rather than restating it in Procedure, Execution Boundaries, and Failure Mode.

Consider moving the Stage Arc Boundary contract detail fully into its referenced file since the inline field list (left_arc, active_arc, etc.) duplicates the referenced contract.

Dimension	Reasoning	Score
Conciseness	Mostly efficient operational prose, but the stop-before-commit/deploy/closure list recurs near-verbatim in the Procedure, Execution Boundaries, and Failure Mode sections, and the Philosophy restates the safety model, so it could be tightened.	2 / 3
Actionability	Provides a copy-pasteable YAML output template with concrete field names (slack_policy, stop_rule_status, next_safe_action) and specific procedure steps with an example validation command, giving actionable guidance for a routing skill.	3 / 3
Workflow Clarity	A clearly sequenced 6-step procedure with explicit validation gates, a fail-fast rule, and a Failure Mode that names the smallest recovery step, supplying the feedback loop the rubric rewards.	3 / 3
Progressive Disclosure	The body is an organized overview with a clearly signaled, one-level-deep References section pointing to real bundle files (phase-gate-contract.md, contract.yaml, evals.yaml) and shared contracts.	3 / 3
	Total	11 / 12 Passed

Description

92%

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

A well-constructed description with concrete actions, explicit trigger guidance, and clear what/when coverage. Its main weakness is moderate overlap with the sibling HE skills it routes into and a slightly generic PR-progress trigger.

Suggestions

Tighten the 'keep this PR moving' trigger to a more distinctive phrasing that cannot collide with generic PR-progress skills.

Signal the compatibility-shim nature up front (e.g. 'Compatibility entrypoint for old phase-heartbeat requests') so it is distinguishable from he-phase-work at trigger time.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('check the approved plan, reuse or create a 10-minute continuation only with authority, run phase gates, delegate the active slice to he-work, and stop before commit or tracker closure'), matching the multiple-specific-actions anchor.	3 / 3
Completeness	Explicitly answers what (routes old phase-heartbeat requests through phase gates and delegation) and when ('Use when a user says phase heartbeat, keep this PR moving, or continue phases').	3 / 3
Trigger Term Quality	'Use when a user says phase heartbeat, keep this PR moving, or continue phases' gives natural phrases a user would actually say, with good coverage of the skill's request surface.	3 / 3
Distinctiveness Conflict Risk	The niche is clear but it explicitly routes into sibling skills (he-phase-work, he-work) and 'keep this PR moving' is generic enough to overlap with other PR-management skills.	2 / 3
	Total	11 / 12 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: jscraik/Agent-Skills
Commit: 5a6027f

Reviewed: 5 days 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.