Maps organizational power dynamics and builds influence without authority using Jeffrey Pfeffer's power frameworks. Use when getting buy-in for ideas, navigating company politics, managing up, or building coalitions across teams.
79
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./influence-craft/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description with excellent trigger terms and completeness. It clearly identifies when to use the skill with natural language triggers and establishes a distinct niche around organizational influence. The main weakness is that the capabilities could be more concrete—specifying deliverables like 'stakeholder maps', 'influence strategies', or 'political landscape analysis' would strengthen specificity.
Suggestions
Add more concrete action outputs such as 'creates stakeholder maps', 'develops influence strategies', or 'analyzes political landscape' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (organizational power dynamics, influence) and references a specific framework (Jeffrey Pfeffer's), but the actions are somewhat abstract ('maps', 'builds influence') rather than listing multiple concrete deliverables or outputs. | 2 / 3 |
Completeness | Clearly answers both what (maps power dynamics, builds influence using Pfeffer's frameworks) and when (explicit 'Use when' clause with four specific trigger scenarios: getting buy-in, navigating politics, managing up, building coalitions). | 3 / 3 |
Trigger Term Quality | Includes natural terms users would actually say: 'buy-in', 'company politics', 'managing up', 'building coalitions'. These are common workplace phrases that match how users would describe their needs. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining organizational politics, influence strategies, and a specific academic framework (Pfeffer). Unlikely to conflict with other skills due to the specific domain of workplace power dynamics. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable framework for organizational influence but leans toward abstract guidance rather than concrete, executable examples. The templates are useful scaffolding but would benefit from completed examples showing real application. The content is moderately concise but includes some filler (activation triggers, quotes) that don't add actionable value.
Suggestions
Replace the fill-in-the-blank stakeholder template with a completed example showing a realistic scenario (e.g., 'Getting buy-in for a new tool adoption')
Remove the 'When This Skill Activates' section and quotes - these consume tokens without adding actionable guidance
Add a 'Signs your approach isn't working' section with specific indicators and pivot strategies to create a feedback loop for influence-building
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary elements like the 'When This Skill Activates' section (Claude knows when to apply skills) and quotes that add little actionable value. The frameworks are presented concisely but could be tighter. | 2 / 3 |
Actionability | Provides templates and checklists which are somewhat actionable, but they're fill-in-the-blank placeholders rather than concrete examples. Missing specific examples of completed stakeholder maps or real influence scenarios that demonstrate application. | 2 / 3 |
Workflow Clarity | The 'Building Political Capital' section shows a sequence, and the checklist provides steps, but there are no validation checkpoints or feedback loops. For influence-building (which can fail), there's no guidance on how to detect if an approach isn't working or how to adjust. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~80 lines), the content is well-organized with clear sections (frameworks, templates, quick reference). No external references needed for this scope, and the structure allows easy navigation between conceptual frameworks and practical templates. | 3 / 3 |
Total | 9 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
53530ef
Table of Contents
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.