sticky

Use when the user wants to set auto-routing mode: on (every task-shaped message routes), auto (intent-verb messages route — default), or off (no auto-routing). Intent-detection runs by default; use this skill to expand to full sticky or disable entirely. Trigger with /hyperflow:sticky, "make hyperflow sticky", "stop using hyperflow", "is hyperflow sticky", "auto-route to hyperflow", "disable hyperflow auto-routing".

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

75%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.

A highly actionable body with exact file formats, output strings, and error recovery, but it carries noticeable redundancy: instructions and example outputs are repeated across Flow/Instructions/Overview/Examples sections, inflating the token budget without adding information. The behavioural contract also overlaps with the DOCTRINE.md reference it cites.

Suggestions

Collapse 'Flow', 'Instructions', 'Overview', and 'Output' into a single short workflow section — they currently restate the same three-step summary four times.

Keep each subcommand's output block in one place only: either 'Subcommand Details' or 'Examples', not both.

Trim or move the 'Behavioural contract' section to the already-referenced DOCTRINE.md, keeping only a summary plus the routing table, since the file itself says the contract lives there.

Dimension	Reasoning	Score
Conciseness	The core material is precise and free of concept over-explanation, but there is real structural duplication: the same subcommand outputs appear in 'Subcommand Details', again in the 'status' examples, and again in 'Examples', while 'Flow', 'Instructions', 'Overview', and 'Output' each restate the same three-step summary. This is tighter than anchor 2's padded verbosity but well short of 'every token earns its place'.	3 / 5
Actionability	Fully executable guidance: exact file path '.hyperflow/.sticky', exact file format (state/since/trigger), exact one-line output strings per subcommand, and an error-handling table with concrete recovery behavior (backup to '.sticky.bak', create '.hyperflow/' if missing).	5 / 5
Workflow Clarity	The Flow section gives a clear four-step sequence and error handling supplies recovery paths (malformed file → backup + treat as OFF), which is above anchor 3. It is not a 5 because the implicit 'hyperflow-mention upgrade' write happens in 'Activation triggers', detached from the execution flow, slightly blurring what the skill itself does versus what the orchestrator does.	4 / 5
Progressive Disclosure	Good structure with clearly signaled one-level-deep references in the Resources section ('[DOCTRINE.md](../hyperflow/DOCTRINE.md)', '[output-style.md](../hyperflow/output-style.md)') and no nested references. Not a 5 because the ~40-line Behavioural contract duplicates content the file itself attributes to DOCTRINE.md, and much of Subcommand Details/Examples could live in a separate reference.	4 / 5
	Total	16 / 20 Passed

Description

95%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.

A strong description: concrete three-state semantics, an explicit 'Use when' clause, and a comprehensive set of natural trigger phrases anchored in distinctive plugin vocabulary. The only weakness is the unmentioned 'status' subcommand despite it being the default.

Dimension	Reasoning	Score
Specificity	The description defines three concrete actions with precise semantics — 'on (every task-shaped message routes)', 'auto (intent-verb messages route — default)', 'off (no auto-routing)' — plus the default intent-detection behavior. It falls short of a 5 only because the 'status' subcommand (the default invocation) is never mentioned, a minor coverage gap.	4 / 5
Completeness	It explicitly answers both questions: what ('set auto-routing mode: on … auto … or off' with each state's behavior) and when ('Use when the user wants to set auto-routing mode' followed by concrete trigger phrases). This matches the anchor for a clear, explicit what-and-when with concrete triggers.	5 / 5
Trigger Term Quality	Six natural trigger phrases are listed — 'make hyperflow sticky', 'stop using hyperflow', 'is hyperflow sticky', 'auto-route to hyperflow', 'disable hyperflow auto-routing' — covering enable, disable, and status-check intents plus the slash command, matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	Every trigger phrase contains the plugin-specific terms 'hyperflow' or 'sticky', giving the skill a clear niche with minimal risk of firing for unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 3 suspicious	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/tons-of-skills-marketplace
Path: plugins/ai-agency/hyperflow/skills/sticky/SKILL.md
Commit: 88dcf65

Reviewed: 3 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.