incoming-request-advisor

Decode an incoming message into a structured breakdown separating the literal ask from the job-to-be-done. Use when a loaded Slack ping, email, mandate, or escalation needs a reply.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

85%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 well-structured, actionable interactive skill with clear workflow checkpoints and concrete examples, penalized mainly for progressive disclosure: the inline template duplicates what template.md should hold, and the referenced example/template files are not present in the bundle.

Suggestions

Add the referenced bundle files (template.md and examples/conversation-flow.md) to the skill so the one-level-deep references resolve, or remove the references if inlining is intentional.

Move the full 12-section template block out of SKILL.md into template.md, leaving a concise pointer, to reduce duplication and improve token efficiency.

Trim the overlap between Key Concepts and Common Pitfalls (e.g., success-criteria-vs-must-haves and over-filling appear in both) to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence without padding basic concepts, though Key Concepts and Common Pitfalls restate overlapping ideas (e.g., over-filling, success-criteria vs must-haves) that could be trimmed slightly.	4 / 5
Actionability	Provides a concrete 12-section template, exactly three numbered clarifying questions, a verbatim 4-option closing menu, and the sticky-note rule (4-8 words) — fully actionable, copy-paste-ready guidance for an instruction skill.	5 / 5
Workflow Clarity	Clear 4-step sequence with explicit checkpoints: 'ask at most 3, one at a time', 'mark none stated', 'scale depth to the message', and an Assumptions-to-Validate feedback loop labeling inferences; not a destructive/batch operation so no cap applies.	5 / 5
Progressive Disclosure	References to template.md and examples/conversation-flow.md are signaled one level deep, but those bundle files are not present in the bundle to verify, and the full 12-section template is inlined in SKILL.md rather than offloaded to template.md.	3 / 5
	Total	17 / 20 Passed

Description

78%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 concrete, third-person, and includes an explicit 'Use when' trigger with natural channel keywords, satisfying both the what and when requirements. Its main limitation is breadth of named actions rather than a single decoded-breakdown action.

Dimension	Reasoning	Score
Specificity	Names the comms/message domain and one concrete action ('decode an incoming message into a structured breakdown separating the literal ask from the job-to-be-done'), but does not list several distinct actions, so it falls short of the 4-anchor 'several specific actions'.	3 / 5
Completeness	Explicitly answers both what ('Decode an incoming message into a structured breakdown...') and when ('Use when a loaded Slack ping, email, mandate, or escalation needs a reply') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural user-facing triggers 'Slack ping, email, mandate, or escalation needs a reply' give good keyword coverage; a few common synonyms (e.g. 'request', 'DM', 'thread') are missing, keeping it just below 5.	4 / 5
Distinctiveness Conflict Risk	The ask-vs-job-to-be-done framing and specific channel list carve a mostly-distinct niche with minor overlap risk against general stakeholder-comms skills; not yet a perfectly isolated niche for 5.	4 / 5
	Total	16 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 2 missing, 6 suspicious	Warning

	Total	14 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/incoming-request-advisor/SKILL.md
Commit: 1b5a524

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.