culture-craft
Designs team culture and sets standards of excellence using David Singleton (Stripe) and Dharmesh Shah (HubSpot) frameworks. Use when building teams, setting cultural values, creating rituals, or establishing excellence standards.
76
70%
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 ./culture-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 well-structured description with explicit 'Use when...' guidance and good trigger term coverage. The main weakness is the lack of specific concrete actions - it tells us the domain and frameworks but not the specific deliverables or tasks it can perform. The named frameworks add distinctiveness but the capability description could be more actionable.
Suggestions
Add specific concrete actions like 'create culture documents', 'design team rituals', 'draft value statements', or 'build excellence rubrics' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (team culture, standards of excellence) and references specific frameworks (David Singleton/Stripe, Dharmesh Shah/HubSpot), but doesn't list concrete actions beyond 'designs' and 'sets standards' - lacks specifics like 'create culture documents', 'define team rituals', or 'draft value statements'. | 2 / 3 |
Completeness | Clearly answers both what (designs team culture, sets standards using specific frameworks) AND when (explicit 'Use when...' clause with four trigger scenarios: building teams, setting cultural values, creating rituals, establishing excellence standards). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'building teams', 'cultural values', 'rituals', 'excellence standards'. These are terms users would naturally use when seeking help with team culture work. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche combining team culture with specific named frameworks (Singleton/Stripe, Shah/HubSpot). The combination of culture design + these specific methodologies creates a distinct trigger profile unlikely to conflict with generic management or HR skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%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 starting structure for culture building with useful templates and checklists, but lacks concrete, actionable examples that show what good looks like in practice. The frameworks are listed at a high level without demonstrating how to actually apply them, and the template uses placeholders rather than filled-in examples that Claude could learn from.
Suggestions
Replace placeholder brackets in the template with at least one fully worked example showing a complete team culture document
Add concrete implementation guidance for each Stripe principle (e.g., 'Bias for action means: respond to Slack within 4 hours, ship MVPs within 2 weeks')
Include validation steps or success metrics to assess whether culture initiatives are working (e.g., 'Survey team quarterly on value alignment')
Remove or condense the quotes section - these don't add actionable guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary framing (e.g., 'When This Skill Activates' section explains obvious triggers). The quotes section adds minimal value and the frameworks could be more condensed. | 2 / 3 |
Actionability | Provides a template structure which is helpful, but the guidance remains abstract with placeholder brackets rather than concrete examples. The frameworks list principles without showing how to actually implement them in practice. | 2 / 3 |
Workflow Clarity | The 'Culture as Competitive Advantage' section provides a 4-step sequence, and the checklist offers structure, but there are no validation checkpoints or feedback loops for assessing whether culture-building efforts are working. | 2 / 3 |
Progressive Disclosure | Content is organized into logical sections with headers, but everything is inline in one file. For a skill of this scope, separating the template into its own file or providing links to detailed framework explanations would improve navigation. | 2 / 3 |
Total | 8 / 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.
- Repository
- menkesu/awesome-pm-skills
- Commit
53530ef
- 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.