CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

culture-architect

Build, measure, and evolve company culture as operational behavior — not wall posters. Covers mission/vision/values workshops, values-to-behaviors translation, culture code creation, culture health assessment, and cultural rituals by stage. Use when building company values, assessing culture health, designing cultural rituals, creating culture codes, handling culture clashes, or when user mentions culture, values, culture debt, founder culture, or culture code.

68

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is culture-architect in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 lean, highly actionable playbook — concrete tables, thresholds, workshop questions, and stage-specific rituals organized in a coherent build→measure→maintain lifecycle. Its weaknesses are the broken reference chain (both cited bundle files are absent from the skill directory) and minor token redundancy from a duplicated Keywords section and repeated reference pointers.

Suggestions

Ship the referenced bundle files or inline their essentials: `references/culture-playbook.md` and `templates/culture-code-template.md` are cited three times but do not exist in the skill directory — either add them (with the survey questions and culture code template) or inline the critical content so the progressive disclosure chain is not broken.

Remove the `## Keywords` section and the `## Detailed References` section: the frontmatter description already carries the trigger terms and each framework already cites its reference inline, so these ~5 lines are redundant token spend.

Add a one-line routing hint near the top (e.g., 'New culture → Frameworks 1–3; existing culture → 4–5; intervention → 6') so Claude knows which framework to enter from for a given request.

DimensionReasoningScore

Conciseness

The body is dense and opinionated with no over-explanation of concepts Claude already knows — behavioral anchors like "Decisions under €5K happen at team level, same day, no approval needed" earn their tokens. Not 5: there is trimmable redundancy — the "## Keywords" section ("culture, company culture, values, mission, vision...") duplicates frontmatter trigger terms, and "## Detailed References" repeats the two inline citations of `references/culture-playbook.md` and `templates/culture-code-template.md`. Not 3: these are minor instances, not 'some unnecessary explanation' spread through the content.

4 / 5

Actionability

For an instruction-only skill, guidance is copy-paste ready: concrete workshop questions ("What would be lost if we disappeared tomorrow?"), a behavioral-anchor table with specific examples, a decision threshold table ("< 50% | Crisis | Culture emergency — all-hands intervention"), and rituals with cadences ("Weekly all-hands (30 min): company update + one win + one learning"). Not 4: no material gaps — specific examples cover the common cases across all six frameworks.

5 / 5

Workflow Clarity

Frameworks are numbered in a coherent build→codify→measure→maintain lifecycle, each with internal checkpoints: the day-30 test ("How would a new hire know we actually live this on day 30?"), the promotion audit ("What did the last person who got promoted demonstrate?"), and quarterly cadence with score-band actions. Not 5: there is no explicit routing for which framework to start from given a user's request, so the top-level sequence is implicit rather than stated. Not 3: checkpoints are present within each framework, not missing or merely implicit.

4 / 5

Progressive Disclosure

References are clearly signaled, described, and one level deep ("See `references/culture-playbook.md` for survey design", "See `templates/culture-code-template.md` for a complete template"), and the body appropriately keeps bulk detail out. However, scoring against the actual bundle structure: neither `references/culture-playbook.md` nor `templates/culture-code-template.md` exists in the skill directory — the bundle contains only SKILL.md — so the disclosure chain is broken and a runtime read would fail. Not 4: missing referenced files are more than a 'minor organization gap'; not 2: the inline content is well-structured and references are prominently signaled, not buried.

3 / 5

Total

16

/

20

Passed

Description

88%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, concrete, comprehensive on 'what', with an explicit 'Use when...' clause covering many natural trigger terms including synonyms like culture debt and founder culture. The only weaknesses are a few missing natural triggers (mission/vision, culture survey) and slight breadth on the generic word 'values'.

DimensionReasoningScore

Specificity

"Build, measure, and evolve company culture as operational behavior" plus "mission/vision/values workshops, values-to-behaviors translation, culture code creation, culture health assessment, and cultural rituals by stage" lists five concrete, named actions with comprehensive coverage. Written in third-person imperative voice matching the good examples. Not 4: the action list is comprehensive with no minor gaps in coverage, which is the anchor-5 distinction over 'minor gaps'.

5 / 5

Completeness

Explicitly answers 'what' ("Covers mission/vision/values workshops, values-to-behaviors translation, culture code creation, culture health assessment, and cultural rituals by stage") and 'when' ("Use when building company values, assessing culture health... or when user mentions culture, values, culture debt, founder culture, or culture code") with concrete trigger phrases. This matches the anchor-5 example pattern exactly; not 4: the 'when' clause is fully explicit and specific, not merely adequate.

5 / 5

Trigger Term Quality

Trigger clause includes natural phrases users would say: "building company values", "assessing culture health", "designing cultural rituals", "creating culture codes", "handling culture clashes", "culture debt, founder culture, or culture code". Not 5: a few natural terms are missing from the 'when' clause — users asking for a 'mission statement', 'vision', or 'culture survey' (concepts the skill covers) would not match; not 3: coverage goes well beyond 'some relevant keywords' with many synonyms and variations present.

4 / 5

Distinctiveness Conflict Risk

The culture-leadership niche is clear and the what/when pairing is specific ("handling culture clashes... founder culture, or culture code"), far above the generic anchor-3 example. Not 5: the bare trigger "values" is a generic word that could overlap with ethics, decision-making, or personal-values skills — a minor overlap risk with closely related skills.

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/culture-architect/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.