CtrlK
BlogDocsLog inGet started
Tessl Logo

novu-human

Ask a human to decide (ask / approve / choose / tell) when the action is risky, irreversible, or a real multi-way choice — not for routine in-thread chat. Use novu_human on managed agents, ctx.ask/approve/choose/tell on code-defined agents, or the human CLI when no one is watching this session.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 tight, well-structured instruction skill that gives concrete per-runtime tool guidance with clear decision criteria and boundary notes. The only gap is the absence of a complete example card/invocation for the managed-agent path, which keeps actionability at 4 rather than 5.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — the opening 'Escalate to a real person when guessing is expensive' and the dense runtime sections carry only actionable specifics (required fields, icon rules, constraints) with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Provides concrete, executable guidance — exact tool names, exact params (kind, card.title, card.options 2–10), exact CLI commands (human ask|approve|choose|tell) — but the managed-agent case never shows a complete example card/invocation shape, leaving a minor gap versus the 'copy-paste ready code covering common cases' 5 anchor.

4 / 5

Workflow Clarity

This is a simple decision-plus-single-action skill: the 'Use it when' criteria, the per-kind guidance (choose for multi-way, tell for notify), and the three unambiguous runtime branches make the action clear, satisfying the simple-skill exception for a 5; the destructive-operation validation cap does not apply because HITL is itself the validation gate.

5 / 5

Progressive Disclosure

Under 50 lines, single-purpose, with no need for external bundle files; the content is organized into a clear intro, a 'Use it when' list, boundary notes, and three runtime subsections, matching the 'well-organized sections' exception for a 5.

5 / 5

Total

19

/

20

Passed

Description

88%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, specific description that clearly states both the capability and when to use it, with concrete tool names per runtime and an explicit negative boundary. Minor room to broaden natural-language trigger synonyms and tighten distinctiveness against generic interaction skills.

DimensionReasoningScore

Specificity

Names multiple concrete actions (ask / approve / choose / tell) plus the three runtime-specific mechanisms (novu_human, ctx.ask/approve/choose/tell, human CLI), giving comprehensive coverage of the domain — matching the 'multiple specific concrete actions; comprehensive coverage' anchor rather than the 4 anchor which implies coverage gaps.

5 / 5

Completeness

Explicitly answers what ('Ask a human to decide (ask / approve / choose / tell)') and when ('when the action is risky, irreversible, or a real multi-way choice — not for routine in-thread chat') with concrete trigger phrasing and explicit negative boundary, matching the 'clearly and explicitly answers both what AND when' anchor.

5 / 5

Trigger Term Quality

Contains natural phrases users would say ('Ask a human', 'risky, irreversible', 'multi-way choice', 'approve', 'choose') alongside specific tool names, giving good keyword coverage; falls short of the 5 anchor because it lacks the full synonym/variation breadth (e.g. 'need approval', 'human in the loop' live in the triggers list rather than the description itself).

4 / 5

Distinctiveness Conflict Risk

Has a clear niche (HITL escalation) with distinctive tool triggers (novu_human, ctx.approve, human CLI) and an explicit 'not for routine in-thread chat' boundary, but natural-language phrases like 'ask the human' carry minor overlap risk with general interaction skills, placing it just below the minimal-conflict 5 anchor.

4 / 5

Total

18

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
novuhq/novu
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.