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.

71

Quality

89%

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

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 an efficient, highly actionable toolkit with concrete questions, quantified behavioral anchors, and score-to-action mappings. Its main defects are a broken bundle reference (`templates/culture-code-template.md` is cited twice but absent) and minor padding (a Keywords section duplicating the frontmatter triggers).

Suggestions

Fix the broken reference: either add `templates/culture-code-template.md` to the bundle or remove the two citations of it (lines 71 and 167), since a Claude following them will hit a dead end mid-workflow.

Delete the "## Keywords" section in the body — trigger terms belong in the frontmatter description, and Claude gains nothing from reading them again in context.

Move the full Values→Behaviors example table and stage ritual details into `references/culture-playbook.md`, keeping only the framework names and one example row inline, so SKILL.md reads as a lean overview with well-signaled references.

DimensionReasoningScore

Conciseness

The body is dense and table-driven with almost no explanation of concepts Claude already knows (e.g., the Bad version vs Behavioral anchor table, score-interpretation table, stage ritual lists). It is not the 5 anchor because of minor padding: the standalone "Keywords" section duplicates trigger terms already in the frontmatter description, and aphoristic lines like "Culture is what you DO, not what you SAY" could be trimmed — but these are small instances, not the 'several unnecessary explanations' of the 3 anchor.

4 / 5

Actionability

For an instruction-only skill the guidance is fully concrete and ready to use: exact workshop questions ("What would be lost if we disappeared tomorrow?"), a value table with quantified behavioral anchors ("Decisions under €5K happen at team level, same day", "share bad news within 24 hours"), a 7-part culture code structure, five named survey areas with example items, and a score-band table mapping percentages to specific actions. Specific examples cover the common cases; the scoring note confirms absence of code is not penalized when guidance is this actionable.

5 / 5

Workflow Clarity

Sequences are present and mostly checkpointed: the workshop is ordered mission→vision→values with a concrete test ("How would a new hire know we actually live this on day 30?"), the assessment workflow has an explicit feedback loop (score bands → prescribed actions, e.g., "< 50% → Crisis — all-hands intervention"), and rituals are sequenced by company stage. Minor gaps — no ordering guidance for when to run which framework, and the culture-code creation steps stop at pointing to the template — keep it below the 5 anchor; no destructive/batch operation applies, so no cap.

4 / 5

Progressive Disclosure

The body is structured as an overview with a clearly signaled "Detailed References" section, and `references/culture-playbook.md` exists and is one level deep. However, the body references `templates/culture-code-template.md` twice (lines 71 and 167) and that file does not exist in the bundle — a broken navigation path. Additionally, the ~60-line Frameworks section with full tables is borderline content that belongs in the reference. This is 'some structure but could be better organized' rather than the 4 anchor's 'minor organization gaps', since one of the two referenced files is missing entirely.

3 / 5

Total

16

/

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: it answers what the skill does and when to use it with concrete, natural trigger phrases in third-person voice. The only residual risk is that very common words like "culture" and "values" could overlap with sibling leadership/HR skills in the same category.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — "mission/vision/values workshops, values-to-behaviors translation, culture code creation, culture health assessment, and cultural rituals by stage" — plus the framing action "Build, measure, and evolve company culture as operational behavior". This matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage'; it is not the 4 anchor because coverage spans the full skill scope with no significant gap.

5 / 5

Completeness

Both halves are explicit: the "what" ("Build, measure, and evolve company culture... Covers..." ) and the "when" with concrete trigger phrases ("Use when building company values, assessing culture health... or when user mentions culture, values, culture debt..."). This mirrors the 5 anchor example structure exactly; the 4 anchor ('when could be more explicit') does not apply since the when-clause enumerates specific scenarios.

5 / 5

Trigger Term Quality

Triggers include natural user phrasings with synonyms and near-synonyms: "building company values, assessing culture health, designing cultural rituals, creating culture codes, handling culture clashes", plus noun mentions "culture, values, culture debt, founder culture, or culture code". Coverage is comprehensive across synonyms; only trivially common variants (e.g., "team culture") are absent, so it sits at the 5 anchor rather than 4.

5 / 5

Distinctiveness Conflict Risk

The niche is mostly distinct — phrases like "culture debt", "culture code", and "values-to-behaviors" are unlikely to fire a generic HR or leadership skill. However, broad single words like "culture" and "values" carry minor overlap risk with adjacent people-ops/leadership skills, so it is 'mostly distinct; minor overlap risk' rather than the minimal-conflict 5 anchor.

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

alirezarezvani/claude-skills

Path

c-level-advisor/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.