CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-feedback

Collect feedback and create GitHub issue (bug report, feature request)

Quality

78%

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 ./.agents/skills/moai-feedback/SKILL.md
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.

The body is an extremely lean, unambiguous delegation stub: it tells Claude exactly one thing — call the 'moai' skill with the 'feedback' subcommand and the passed arguments — with zero wasted tokens. Its only weakness is that argument semantics and the feedback workflow are entirely undocumented here, leaving a minor actionability gap.

DimensionReasoningScore

Conciseness

The body is a single lean line — 'Use Skill("moai") with arguments: feedback $ARGUMENTS' — with no padding, no explanation of concepts Claude already knows, and nothing that could be trimmed. It matches 'Lean and efficient; assumes Claude's competence; every token earns its place'.

5 / 5

Actionability

The body gives one concrete, executable instruction with an exact skill name and subcommand, which is copy-paste-ready guidance. It falls short of a 5 because valid arguments and the expected feedback flow are unspecified — a minor gap left entirely to the delegated 'moai' skill.

4 / 5

Workflow Clarity

This is a simple single-purpose skill whose single action — invoke the 'moai' skill with 'feedback <args>' — is unambiguous, so the simple-skill exception applies and workflow clarity can score 5. Creating a GitHub issue is not a destructive or batch operation, so the validation cap does not apply.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (no references/, scripts/, or assets/ directories exist), and its delegation to Skill("moai") is a single clearly signaled pointer. Per the scoring notes for such simple skills, progressive disclosure scores 5.

5 / 5

Total

19

/

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 states a clear purpose (collecting feedback and filing GitHub issues for bug reports and feature requests) but is incomplete as a trigger: it has no explicit 'Use when...' guidance and only a thin set of trigger keywords without synonyms. It is distinct enough to avoid most conflicts, yet users asking to 'report a bug' or 'file an issue' may not reliably surface it.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user wants to report a bug, request a feature, or give feedback on the moai tool'.

Include natural trigger synonyms and phrasings such as 'report a bug', 'file an issue', 'suggest a feature', and 'submit feedback' alongside the existing terms.

Make the 'what' more concrete by specifying how feedback is collected (e.g., 'Asks the user a short set of questions, then files the response as a GitHub issue').

DimensionReasoningScore

Specificity

"Collect feedback and create GitHub issue" names the domain with two actions, but "Collect feedback" is generic (how feedback is gathered is unstated) and "(bug report, feature request)" is a scope qualifier rather than an additional action. This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'; it lacks the several distinct actions needed for a 4.

3 / 5

Completeness

The 'what' is clear (collect feedback, create a GitHub issue for bug reports or feature requests), but there is no 'Use when...' clause or equivalent explicit trigger guidance. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3, matching the anchor 'Has a clear what but when is missing or only weakly implied'.

3 / 5

Trigger Term Quality

"feedback", "GitHub issue", "bug report", and "feature request" are natural user phrases, but the description omits common variations and synonyms (e.g., "report a bug", "file an issue", "suggest a feature"). Coverage sits between anchor 3 (missing common variations) and anchor 4 (good coverage, a few missing), closer to 3 given how thin the term set is.

3 / 5

Distinctiveness Conflict Risk

"create GitHub issue (bug report, feature request)" carves a fairly specific niche that is distinguishable from general document or data skills, though it could overlap with other GitHub-workflow or feedback skills. This fits 'Mostly distinct; minor overlap risk with closely related skills'; it lacks the explicit distinct trigger phrases of a 5.

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

modu-ai/moai-adk

Path

.agents/skills/moai-feedback/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.