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

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Quality

Content

78%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 well-structured and actionable, with a concrete output template, explicit validation gates, and clean progressive disclosure to verified reference files. Main weaknesses are repeated stop-rule enumeration and a delegated rather than in-skill retry loop.

Suggestions

Deduplicate the stop-rule list: state the full enumeration once (e.g., in Execution Boundaries) and reference it from the Procedure step instead of repeating all eight actions.

Add a brief in-skill validate->fix->revalidate note in the Procedure or Validation Gates section rather than fully delegating the retry loop to he-work.

Tighten 'run the phase gate contract' in step 4 with a one-line summary of what the gate checks, so the core procedure is actionable without opening the reference.

Dimension	Reasoning	Score
Conciseness	The body is lean with short, well-organized sections and no over-explanation of known concepts, but the eight-item stop-rule enumeration ('staging, commit, merge, review-thread resolution, Linear closure, deploy, or destructive cleanup') is repeated across the Procedure and Execution Boundaries sections and could be tightened.	4 / 5
Actionability	A concrete copy-pasteable YAML output template with exact fields and example commands ('bash scripts/verify-work.sh --fast', 'slack_policy: blocked') plus a specific numbered procedure gives mostly executable guidance; steps like 'run the phase gate contract' defer detail to a reference file.	4 / 5
Workflow Clarity	A clear six-step sequence with an explicit fail-fast rule and a Validation Gates checklist is present, but the validate->fix->retry feedback loop is delegated to he-work rather than spelled out in-skill, leaving a minor validation gap.	4 / 5
Progressive Disclosure	SKILL.md serves as a clear overview with a well-signaled References section pointing one level deep to real bundle files (phase-gate-contract.md, contract.yaml, evals.yaml) and shared contracts, with content appropriately split out.	5 / 5
	Total	17 / 20 Passed

Description

83%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 concisely states a concrete routing workflow and gives explicit, natural trigger phrases for when to use it. Its only weakness is minor overlap with the related he-phase-work skill and process-level rather than tool-level action wording.

Dimension	Reasoning	Score
Specificity	Lists several concrete routing actions ('check the approved plan, reuse or create a 10-minute continuation... run phase gates, delegate the active slice to he-work, and stop before commit or tracker closure') but they are stated at a process level rather than as discrete tool capabilities, leaving minor coverage gaps.	4 / 5
Completeness	Clearly answers what (routes old phase-heartbeat requests into HE phase work with enumerated actions) and explicitly states when with concrete trigger phrases, matching the anchor for both what and when.	5 / 5
Trigger Term Quality	'Use when a user says phase heartbeat, keep this PR moving, or continue phases' provides good coverage of natural user phrases, with metadata trigger_terms adding 'recurring phase work'; a few synonymous phrasings a user might say are still missing.	4 / 5
Distinctiveness Conflict Risk	The heartbeat framing and trigger phrases carve a clear niche, but it is explicitly a compatibility shim for the closely related he-phase-work skill, creating minor overlap risk with that sibling.	4 / 5
	Total	17 / 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: jscraik/Agent-Skills
Path: Plugins/harness-engineering/skills/he-phase-heartbeat/SKILL.md
Commit: 2f91362

Reviewed: 1 day 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.