CtrlK
BlogDocsLog inGet started
Tessl Logo

management-talk

Rewrite engineer-to-engineer content for engineering-org leadership (VPs, directors, PMs, release managers, execs in an engineering-savvy company) and shape it for the channel it is going to — JIRA comment, Slack post, async standup line, email, or meeting talking-points. Trigger when the user asks to write/rewrite for management / exec / VP / director / PM / release manager, asks for an "executive summary / leadership update / status update", says "make this less technical / less jargony", or asks for a slack / email / standup / meeting version of work originally written engineer-to-engineer.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

A well-crafted, actionable writing-style skill with concrete channel shapes, explicit posting guardrails, and a useful worked example. Minor room to tighten the worked example and fold the validation rules more tightly into the output flow.

Suggestions

Tighten the three-channel worked example (e.g., trim the full JIRA block to the building blocks actually being demonstrated) to lift conciseness toward the top anchor.

Inline the 'Never invent facts / owners' and 'Get sign-off before posting' checks as explicit steps inside the Output flow so validation checkpoints are sequenced, not only listed in Rules.

Consider moving the channel-by-channel shape details into a references file if the body grows further, to keep SKILL.md as a lean overview with one-level-deep navigation.

DimensionReasoningScore

Conciseness

Mostly lean, assumes Claude knows what JIRA/Slack are, and avoids explaining basic concepts; the three-channel worked example is long but illustrative rather than padded, with only minor trimmable instances keeping it off the top anchor.

4 / 5

Actionability

Highly concrete guidance: channel-specific length targets ('under ~80 words', 'under ~40'), a standup sentence pattern with copy-ready examples, and JIRA building blocks; specific examples cover all common channels.

5 / 5

Workflow Clarity

A clear numbered Output flow with an explicit sign-off validation gate ('wait for explicit "post it" / "go ahead" / "yes"') and a feedback loop ('one iteration is normal, three is a smell'); not a 5 because the validation checkpoints live partly in the Rules section rather than being fully inline in the flow.

4 / 5

Progressive Disclosure

Well-organized single-file body with clear section headers and navigation (When to invoke, Tone, Channel shapes, Output flow, Rules); no external references are used, and the content is cohesive, but the skill exceeds 50 lines so the small-skill 5-exception does not apply.

4 / 5

Total

17

/

20

Passed

Description

95%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.

A strong description: third-person voice, explicit what-and-when, and rich natural trigger phrases with synonyms. The only minor gap is a narrow action vocabulary (rewrite/shape), which keeps specificity just below the top anchor.

DimensionReasoningScore

Specificity

Two concrete actions are named ('Rewrite engineer-to-engineer content for engineering-org leadership' and 'shape it for the channel') with five channels enumerated (JIRA, Slack, standup, email, talking-points); not a 5 because the core action vocabulary is narrow (rewrite/shape) rather than many distinct operations.

4 / 5

Completeness

Explicitly states what it does (rewrite + shape for channel) and when to use it via a concrete 'Trigger when...' clause with multiple trigger phrases; clearly answers both what and when.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases are quoted verbatim ('make this less technical / less jargony', 'executive summary / leadership update / status update', 'slack / email / standup / meeting version') with role synonyms (management / exec / VP / director / PM / release manager); matches the comprehensive-synonym anchor.

5 / 5

Distinctiveness Conflict Risk

Clear niche (engineering content → engineering-org leadership, specific channel set) with a precisely scoped audience definition ('engineering-savvy company', 'read code names but not code'); minimal overlap risk with generic status-report skills.

5 / 5

Total

19

/

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
thananon/9arm-skills
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.