CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cyberstrike-pi-demo

满配示例技能包:SKILL.md + scripts/、references/、assets/ 等可选目录;验证 Pi skill 与 HTTP 包内路径(仅授权安全测试与教学)。

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/cyberstrike-pi-demo/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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-organized and token-efficient, with a clearly sequenced authorized-testing workflow, explicit validation checkpoints, concrete API endpoints, and a verification checklist. Its main defects are two references to nonexistent files (FORMS.md, REFERENCE.md) and the absence of expected-outcome examples or error-recovery loops in the verification workflow.

Suggestions

Create or remove the missing FORMS.md and REFERENCE.md referenced in the intro paragraph — following those references currently dead-ends, which is the body's only progressive-disclosure failure.

Add expected outcomes for the verification steps (e.g. which JSON fields should appear in the GET /api/skills response) so verification is checkable rather than just executable.

DimensionReasoningScore

Conciseness

The body is dense and efficient — tables for the payload examples, references/assets mapping, and tool chain, plus a final checklist — with no explanation of concepts Claude already knows. It is not 5 because the opening paragraph explaining Agent Skills packaging conventions and the package's own meta-structure could be trimmed, and not 3 because there is no significant padding or unnecessary explanation.

4 / 5

Actionability

Concrete, near-executable guidance appears throughout: "GET /api/skills/cyberstrike-pi-demo?depth=summary|full", "resource_path=scripts/check-env.sh", specific probe strings, and named tools (Burp Suite, ffuf, nuclei, sqlmap). It is not 5 because no complete executable commands (e.g. full curl examples) or expected-response examples are given, and not 3 because the guidance is specific and concrete rather than pseudocode or high-level hints.

4 / 5

Workflow Clarity

The 授权测试工作流 section gives a clear five-step sequence with explicit checkpoints — step 1 scope confirmation and step 3 "高风险操作前二次确认授权边界" — reinforced by a final 清单与验证 checklist, so the destructive/batch validation cap is not triggered. It is not 5 because there are no error-recovery feedback loops (what to do when a verification step fails), and not 3 because validation checkpoints are explicit rather than implicit.

4 / 5

Progressive Disclosure

Section structure is good and the path/purpose table clearly signals real bundle files (references/citations.md, assets/README.txt, scripts/payloads.txt), but the intro states "补充说明见 FORMS.md、REFERENCE.md" and neither file exists in the bundle — two dead references that break navigation. Scored against the actual bundle structure, this is more than the 'minor organization gaps' of level 4, fitting level 3 despite the otherwise decent organization.

3 / 5

Total

15

/

20

Passed

Description

53%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 clearly states what the bundle is and its single verification purpose, giving it a distinct niche, but it omits any explicit 'use when' trigger guidance and its keywords lean toward structural/technical identifiers rather than phrases a user would naturally say. This caps completeness and trigger-term quality at the midpoint.

Suggestions

Add an explicit trigger clause, e.g. 'Use when testing CyberStrike Pi skill-package listing, depth, section, or resource_path endpoints' — this would raise completeness from 3 to 4-5.

Include natural trigger keywords and synonyms users would actually say ('skill package', 'resource_path', '包内路径读取', 'skill 索引/API') alongside the technical directory names.

Enumerate the concrete verification actions individually (list skills via GET /api/skills, fetch sections via section=, read bundled resources via resource_path) instead of compressing them into one clause.

DimensionReasoningScore

Specificity

The description names its domain ("SKILL.md + scripts/、references/、assets/ 等可选目录") and one concrete action ("验证 Pi skill 与 HTTP 包内路径"), matching the anchor for domain plus 1-2 concrete actions. It is not 4 because it does not enumerate several distinct actions, and not 2 because the stated verification action is concrete rather than generic.

3 / 5

Completeness

The 'what' is clearly stated (a fully-configured example skill package that verifies Pi skill and HTTP in-package paths), but there is no 'Use when...' clause or equivalent trigger guidance — the parenthetical "(仅授权安全测试与教学)" is a scope restriction, not a usage trigger, so completeness is capped at 3 per the rubric guideline. Not 2 because the 'what' is clear, not 4 because 'when' is entirely missing.

3 / 5

Trigger Term Quality

Terms like "Pi skill", "HTTP 包内路径", and "scripts/" are relevant to a developer testing this package API, but they are structural/technical identifiers rather than natural user phrases, and common variations (e.g. "skill package", "resource_path", listing/depth/section retrieval) are absent. This fits 'some relevant keywords but missing common variations' rather than the good coverage of level 4.

3 / 5

Distinctiveness Conflict Risk

The niche is distinct — verifying Pi skill-package and HTTP in-package path handling — with little overlap risk against unrelated skills. It is not 5 because the trailing "授权安全测试与教学" scope partially overlaps generic authorized-security-testing skills and the description lacks distinct natural-language triggers.

4 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

AIPentest/CyberStrikeAI

Path

skills/cyberstrike-pi-demo/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.