CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

report-issue

Use when the user wants to report a bug, file an issue, submit a bug report, or report any problem with the mobile-app plugin.

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 ./plugins/mobile-apps/skills/report-issue/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

96%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 lean, fully executable read-only workflow: concrete commands, verbatim prompts, a complete issue template, explicit checkpoints, and a thoughtful sensitive-data exclusion list. The only structural nit is that the large template and unverifiable plugin-root references leave progressive disclosure slightly short of ideal.

DimensionReasoningScore

Conciseness

Every block is operational — bash commands, verbatim prompt text, a runnable node heredoc, the issue template, and a do-not-capture list — with no explanations of concepts Claude already knows. The one-line arrow workflow summary is the only duplication and serves as an at-a-glance map, so this fits anchor 5 rather than 4.

5 / 5

Actionability

Commands are copy-paste ready and complete (e.g., the lockfile version-comparison node script, the environment detection block, the full markdown issue-body template with every placeholder explained). Guidance covers the common cases, matching anchor 5.

5 / 5

Workflow Clarity

Five explicitly sequenced steps each carry a telemetry checkpoint, with conditionals handled ("If $ARGUMENTS contains a description... Otherwise prompt", "If in a project:") and pre-submission verification gates ("sanitize for secrets first", "Review for any sensitive values before submitting", "Do not auto-open without confirmation"). The skill is read-only, so the destructive-operation validation cap does not apply; anchor 5 fits.

5 / 5

Progressive Disclosure

Good structure with clearly signaled one-level-deep references (shared-instructions.md flagged "read this first"), but the reviewed bundle contains no references/ or scripts/ files to verify the ${PLUGIN_ROOT} paths against, and the ~70-line issue-body template is inlined. Minor organization gaps keep this at anchor 4 rather than 5.

4 / 5

Total

19

/

20

Passed

Description

56%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 has strong trigger coverage and clear plugin-scoped distinctiveness, but it omits any statement of what the skill actually does. Adding a capability clause (e.g., generating a fully-populated GitHub issue body for the mobile-app plugin) would fix the completeness gap and raise specificity.

Suggestions

Lead with a capability statement such as "Generates a fully-populated GitHub issue body (description, category, severity, environment, diagnostics) for the mobile-app plugin" before the "Use when..." clause, so both "what" and "when" are explicit.

Add natural trigger synonyms like "open a GitHub issue" or "create an issue" to cover common user phrasings.

Briefly name the diagnostic capability (collecting environment info, package versions, and error logs) to broaden the specificity of capabilities described.

DimensionReasoningScore

Specificity

"report a bug, file an issue, submit a bug report" names the domain (issue reporting for the mobile-app plugin) with concrete action phrases, but these are near-synonymous trigger phrasings rather than a coverage of capabilities — the skill's actual output (generating a formatted GitHub issue body with diagnostics) is never stated. Not 4: it does not list several specific, distinct actions.

3 / 5

Completeness

The description is entirely a "Use when..." trigger clause with no statement of what the skill does — anchor 2 ("only 'when' is present without 'what'") matches exactly. Not 3: the "what" is not even weakly implied; nothing indicates the skill generates a populated issue body.

2 / 5

Trigger Term Quality

"report a bug, file an issue, submit a bug report, or report any problem" provides good natural phrasing users would actually say. Not 5: common variations like "GitHub issue", "open an issue", or "create an issue" are missing.

4 / 5

Distinctiveness Conflict Risk

Scoping to "the mobile-app plugin" gives a clear niche with distinct triggers and minimal risk of firing for unrelated skills. Confirmed against anchor 4: it is not merely "mostly distinct" — the plugin-specific scope makes conflict unlikely.

5 / 5

Total

14

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 missing, 1 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

16

Passed

Repository

microsoft/power-platform-skills

Path

plugins/mobile-apps/skills/report-issue/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.