CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

luffy-arm-fullpower-off

Use when the user asks to turn off, disable, close, or disarm luffy-arm full-power mode, including "turn off full power", "disable full-power", 关闭 full power, 退出全功率模式. Removes the dedicated admin key, verifies that credential is off, and reports alternate user-level SSH access separately.

Quality

85%

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

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 a dense, actionable runbook with genuine validation checkpoints and error-recovery loops for a risky credential operation. Its weaknesses are structural: routing cases and the legacy procedure are interleaved, and some sentences are convoluted enough to slow execution.

Suggestions

Restructure the Operation section as an explicit decision list (registered target → session target → all connections → legacy default key) so the routing order is unambiguous before the numbered legacy steps.

Tighten repeated qualifiers ("with host execution", "explicitly selected") and split the long sandbox/host-execution sentence into a short directive to improve scannability.

State where TARGET syntax is defined (e.g., a one-line pointer to the main skill's target-selection rules) so the off commands are self-contained.

DimensionReasoningScore

Conciseness

The body contains no explanations of known concepts and every line carries operational content, but convoluted phrasing ("in a known sandboxed runtime, request narrowly scoped, user-approved host execution") and repetition ("with host execution", "explicitly selected") could be trimmed. Efficient with minor instances of over-writing, matching anchor 4.

4 / 5

Actionability

Provides concrete, runnable commands ("python3 scripts/power.py off TARGET", "python3 scripts/lifecycle.py all off", "python3 scripts/session.py off TARGET", "bash scripts/fullpower-off.sh") with defined output markers. Not 5 because TARGET selection syntax and the main skill's script paths are deferred without inline resolution, leaving minor gaps.

4 / 5

Workflow Clarity

Validation is explicit and layered (report OFF "only when that credential receives an explicit authentication denial", second-layer "EFFECTIVE USER ACCESS: AVAILABLE" check, UNKNOWN retry via host execution, remediation relay), so the destructive-operation cap does not apply. Falls short of 5 because the three unnumbered routing paragraphs interleaved with the numbered legacy procedure make the overall sequence harder to follow than a clean decision-first flow.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, with well-organized sections and clearly attributed one-level-deep references ("Read the sibling luffy-arm skill's Full-power mode section", "read the main skill's references/user-sessions.md"). The referenced bundle file scripts/fullpower-off.sh exists and matches the body's description. Matches the simple-skill exception for a well-organized short skill.

5 / 5

Total

17

/

20

Passed

Description

87%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 explicit, third-person, and trigger-rich, with a clear what/when pair and bilingual trigger examples. It is a strong description whose only gaps are slightly incomplete action coverage and a few missing English trigger synonyms.

DimensionReasoningScore

Specificity

"Removes the dedicated admin key, verifies that credential is off, and reports alternate user-level SSH access separately" lists several concrete actions. Not 5 because the description omits what the body covers for password-session and all-connections variants; not 3 because it goes beyond 1-2 actions.

4 / 5

Completeness

Explicitly answers both: "Use when the user asks to turn off, disable, close, or disarm luffy-arm full-power mode, including..." (when, with concrete trigger phrases) and the third-person action sentence (what). Clearly matches the top anchor.

5 / 5

Trigger Term Quality

Strong natural-term coverage: "turn off, disable, close, or disarm" plus quoted phrases "turn off full power", "disable full-power", 关闭 full power, 退出全功率模式. A few natural English variants (e.g., "exit full power mode") are missing, so it falls just short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Names a narrow, product-specific niche ("luffy-arm full-power mode") with directional OFF-only triggers, making it clearly distinguishable from the sibling luffy-arm skill and any other skill. Minimal conflict risk.

5 / 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

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

15

/

16

Passed

Repository

Ares960826/luffy-arm

Path

skills/luffy-arm-fullpower-off/SKILL.md

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.