luffy-arm-fullpower-on

Use when the user explicitly asks to turn on, enable, open, or arm luffy-arm full-power mode, including "turn on full power", "enable full-power", 打开 full power, 开启全功率模式. Check layered host status first and reuse an already-ON dedicated gate; gate state and effective ADMIN_USER access are distinct. The agent never loads the key for them.

Quality

81%

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

88%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 a strong, executable, well-sequenced workflow with concrete commands, explicit validation checkpoints, and a clear outcome taxonomy, supported by a real referenced bundle script. Its only weakness is moderate verbosity in the four-case status matrix and reliance on a sibling skill for invariants.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and assumes Claude's competence (no generic explanations), but the four-outcome status matrix and repeated qualifiers ('do not ask the user to re-enter...', 'never translate UNKNOWN to OFF') add some padding that could be tightened.	4 / 5
Actionability	Provides a fully executable command (`bash scripts/fullpower.sh status`, `bash scripts/fullpower-on.sh [seconds]`) with concrete status strings (DEDICATED GATE: ON/UNKNOWN/OFF) and explicit next actions for each branch; copy-paste ready.	5 / 5
Workflow Clarity	A numbered 5-step sequence with an explicit pre-arm status check, condition branches, a user-run-then-confirm checkpoint, a post-run re-check, and a defined outcome taxonomy; strong validation and feedback-loop structure throughout.	5 / 5
Progressive Disclosure	Well-organized into Operation steps with the executable script split into a real bundle file (scripts/fullpower-on.sh) that the body references one level deep; it leans on a sibling skill's section rather than inlining, and the dense status matrix is inline rather than extracted, keeping it just below 5.	4 / 5
	Total	18 / 20 Passed

Description

75%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 specific, trigger-rich, and clearly scoped to the ON operation, with both 'what' and 'when' answered and good distinctiveness. The main weakness is that it bundles several operational invariants (host status, ADMIN_USER access, never-loads-the-key) into the description that belong in the body, slightly diluting the trigger clarity.

Suggestions

Move the invariant clauses ("Check layered host status first...", "gate state and effective ADMIN_USER access are distinct", "The agent never loads the key") into the body; keep the description focused on what + when triggers.

Add a concise canonical trigger phrase (e.g. "Use when the user asks to turn on luffy-arm full-power mode") before listing the synonym variants.

Trim the embedded technical qualifiers so the description reads as a one-sentence trigger, not a mini-procedure.

Dimension	Reasoning	Score
Specificity	Names concrete actions (turn on/enable/open/arm full-power mode, check layered host status, reuse an ON dedicated gate) and states an explicit non-action (never loads the key); not a fully comprehensive action list, so below 5.	4 / 5
Completeness	Clearly answers what (enable full-power mode) and when (explicit user request to turn on/enable/open/arm), with concrete trigger phrases; the long embedded invariant clauses about host status and ADMIN_USER access add context but make the 'when' slightly less crisp than the 5-anchor.	4 / 5
Trigger Term Quality	Includes natural English triggers ("turn on full power", "enable full-power", "open", "arm") plus Chinese variants (打开 full power, 开启全功率模式); the technical "luffy-arm full-power mode" phrasing and absence of a short canonical phrase keep it just below 5.	4 / 5
Distinctiveness Conflict Risk	The highly specific "luffy-arm full-power" trigger and explicit "explicit ON companion" framing make it clearly distinct from generic skills and from the sibling OFF operation; minor overlap risk with the sibling luffy-arm skill itself keeps it just below 5.	4 / 5
	Total	16 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: Ares960826/luffy-arm
Path: skills/luffy-arm-fullpower-on/SKILL.md
Commit: 8ee95ed

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.