CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

influence

Builds a stakeholder map and an influence plan for getting buy-in from executives, founders, peers, engineering, sales or legal, then scripts the pitch, the pushback and the follow-up. Use it for stakeholder management, managing up, getting buy-in, handling a founder's pet idea, disagreeing with the CEO, saying no to a flood of requests, or building trust as a new PM. Draws on 140 Lenny's Podcast guests incl. Jessica Fain, Jeffrey Pfeffer and Hilary Gridley.

Quality

95%

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

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.

Excellent instructional content: fully actionable scripts, a sequenced workflow with explicit exit criteria and error-recovery guidance, and a clean one-level-deep reference structure. The only real cost is token efficiency — the receipts section duplicates the quotes reference and the constant guest-name citations could be thinned.

Suggestions

Remove or compress the "Receipts" section — the six quoted lines with timestamps duplicate references/quotes.md, which the "Go deeper" section already points to; keep at most one anchor quote in the body.

Thin the inline guest citations (e.g., collapse "(Zhang, Gupta, Jason Shah)"-style clusters to a single name) in plays A–G; the full attributions already live in references/frameworks.md, and "Grade existing work" already re-cites the relevant guests per criterion.

DimensionReasoningScore

Conciseness

The body is dense, non-obvious expert guidance with almost no explanation of concepts Claude already knows, but there is trimmable fat: the "Receipts" section duplicates six quotes that live in references/quotes.md, and inline name citations ("(Fain)", "(Pfeffer, Terry)") appear on nearly every line. Not 3: the verbosity is minor padding around genuinely useful content; not 5: the receipts duplication and citation density are tokens that could be cut or moved to the reference file.

4 / 5

Actionability

The skill gives copy-paste-ready material throughout: exact scripts ("Tell me what the board is pushing you on", "how strongly do you feel about this?"), a fill-in deliverable template with every cell specified, a 7-criterion grading rubric with point anchors, and named first moves. Not 4: guidance is executable end-to-end, covering the common cases (pitch, disagreement, overload, new-role trust).

5 / 5

Workflow Clarity

The sequence is explicit (Diagnose with max-4 questions → Pick the play via routing table → Run plays → Deliverable), with validation-style checkpoints ("Done when every critical-path person has a stance, a failure fear, an evidence type and a named first move"), stop conditions ("Climb one rung at a time; stop when it resolves"), and error-recovery loops ("If the objection is fatal, rethink the pitch"). Not 4: exit criteria, error handling, and a completion checklist are all explicitly present.

5 / 5

Progressive Disclosure

The body is a well-organized overview-plus-operating-instructions, with both bundle files (references/frameworks.md, references/quotes.md) verified to exist, clearly signaled one level deep in the "Go deeper" section with descriptions of what each contains. Not 4: navigation is easy, the split is appropriate (compressed plays inline, deep material in references), and there is no nesting or burying.

5 / 5

Total

19

/

20

Passed

Description

96%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: concrete multi-part capability statement, an explicit and richly synonymed 'Use it for' trigger clause, and third-person voice throughout. The only weakness is minor overlap risk with adjacent communication and management skills.

DimensionReasoningScore

Specificity

"Builds a stakeholder map and an influence plan for getting buy-in from executives, founders, peers, engineering, sales or legal, then scripts the pitch, the pushback and the follow-up" names multiple specific concrete actions with named deliverables (map, plan, scripts), covering the full workflow. Not 4: coverage within the domain is comprehensive rather than having minor gaps.

5 / 5

Completeness

It explicitly answers both what ("Builds a stakeholder map and an influence plan... scripts the pitch, the pushback and the follow-up") and when ("Use it for stakeholder management, managing up, getting buy-in...") with concrete trigger phrases. Not 4: the 'when' is fully explicit with multiple specific triggers, not vague.

5 / 5

Trigger Term Quality

"stakeholder management, managing up, getting buy-in, handling a founder's pet idea, disagreeing with the CEO, saying no to a flood of requests, or building trust as a new PM" provides comprehensive natural trigger phrases including synonyms (buy-in / stakeholder management / managing up). Not 4: the trigger list spans the skill's whole surface with natural phrasing a user would actually say.

5 / 5

Distinctiveness Conflict Risk

"scripts the pitch" and "building trust as a new PM" overlap slightly with adjacent comms, feedback, and onboarding-type skills, so it is mostly distinct with minor overlap risk. Not 5: unlike a niche with file-type triggers, workplace-influence territory is shared with closely related management skills; not 3: distinctive triggers like "handling a founder's pet idea" and "disagreeing with the CEO" are clearly specific.

4 / 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

menkesu/awesome-pm-skills

Path

skills/influence/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.