guidance

Answer user questions about QwenPaw installation and configuration: first locate and read local documentation, then distill the answer; if local information is insufficient, fall back to the official website documentation.

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./src/qwenpaw/agents/skills/guidance-en/SKILL.md

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.

The body is highly actionable with executable bash covering a thorough fallback chain and a clear five-step workflow, but it carries some redundant narration around the commands and inlines script-like content that could be split out.

Suggestions

Trim the restating prose between bash blocks (e.g., the "If there is no documentation directory in memory, continue with the following logic." lead-ins) since the commands and comments already convey the flow.

Move the larger path-detection bash into a script under scripts/ and reference it, reducing inline weight and improving progressive disclosure.

Add an explicit verification checkpoint (e.g., confirm the located doc's filename/topic actually matches the question before extracting) to strengthen the workflow's feedback loop.

Dimension	Reasoning	Score
Conciseness	Mostly efficient bash-centric content, but several prose sentences ("First, check whether there is a documentation directory in memory...", "If there is no documentation directory in memory, continue with the following logic.") repeat what the following commands already show and could be trimmed.	3 / 5
Actionability	Provides fully executable, copy-paste-ready bash for every fallback path (built-in DOCS_DIR, memory, source-code path deduction, working-dir search), covering the common cases concretely.	5 / 5
Workflow Clarity	A clear five-step sequence with ordered fallback branching and existence checks as implicit checkpoints; lacks explicit validation/feedback-loop steps, but the read-only lookup is not destructive so the workflow-clarity cap does not apply.	4 / 5
Progressive Disclosure	Well-organized into labeled sections with no nested references and no bundle files to misroute, though ~140 inlined lines (including multi-step bash) could plausibly live in a referenced script rather than inline.	4 / 5
	Total	16 / 20 Passed

Description

58%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 skill does and ties it to a distinct product niche, but it omits an explicit "Use when..." trigger clause and lacks keyword synonyms, capping completeness and trigger-term quality at the mid-range.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about QwenPaw installation, setup, environment configuration, or dependency requirements."

Broaden trigger terms with natural synonyms (setup, env, dependencies, common options) so the description matches how users actually phrase these questions.

Tighten the procedural framing ("first locate... then distill... fall back...") into a capability statement so specificity reads as listed actions rather than a workflow.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("locate and read local documentation", "distill the answer", "fall back to the official website documentation") for the named QwenPaw domain, with only minor coverage gaps.	4 / 5
Completeness	The "what" is clear (answer Q&A about QwenPaw install/config), but there is no explicit "Use when..." trigger clause, capping completeness at 3 per the missing-trigger guideline.	3 / 5
Trigger Term Quality	"QwenPaw installation and configuration" provides the core natural terms, but common synonyms (setup, env, dependencies, options) that users might say are absent from the description.	3 / 5
Distinctiveness Conflict Risk	The unique "QwenPaw" product name gives it a clear niche with low conflict risk, though the generic "installation and configuration" triggers could overlap with a sibling QwenPaw skill.	4 / 5
	Total	14 / 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
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: agentscope-ai/QwenPaw
Path: src/qwenpaw/agents/skills/guidance-en/SKILL.md
Commit: 2094e07

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