skills/c-level-advisor/culture-architect/SKILL.md
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.
npx skillsauth add neekware/ehayeskills culture-architectInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Culture is what you DO, not what you SAY. This skill builds culture as an operational system — observable behaviors, measurable health, and rituals that scale.
culture, company culture, values, mission, vision, culture code, cultural rituals, culture health, values-to-behaviors, founder culture, culture debt, value-washing, culture assessment, culture survey, Netflix culture deck, HubSpot culture code, psychological safety, culture scaling
Culture = (What you reward) + (What you tolerate) + (What you celebrate)
If your values say "transparency" but you punish bearers of bad news — your real value is "optics." Culture is not aspirational. It's descriptive. The work is closing the gap between stated and actual.
Run this conversationally, not as a corporate offsite. Three questions:
Mission — Why do we exist (beyond making money)?
Vision — What does winning look like in 5–10 years?
Values — What behaviors do we actually model?
This is the work. Every value needs behavioral anchors or it's decoration.
| Value | Bad version | Behavioral anchor | | -------------- | ---------------------------- | ---------------------------------------------------------------------------------------- | | Transparency | "We're open and honest" | "We share bad news within 24 hours, including to our manager" | | Ownership | "We take responsibility" | "We don't hand off problems — we own them until resolved, even across team boundaries" | | Speed | "We move fast" | "Decisions under €5K happen at team level, same day, no approval needed" | | Quality | "We don't cut corners" | "We stop the line before shipping something we're not proud of" | | Customer-first | "Customers are our priority" | "Any team member can escalate a customer issue to leadership, bypassing normal channels" |
Workshop exercise: Write your value. Then ask "How would a new hire know we actually live this on day 30?" If you can't answer concretely, it's not a value — it's an aspiration.
A culture code is a public document that describes how you operate. It should scare off the wrong people and attract the right ones.
Structure:
See templates/culture-code-template.md for a complete template.
Anti-patterns to avoid:
Run quarterly. 8–12 questions. Anonymous. See references/culture-playbook.md for survey design.
Core areas to measure:
Score interpretation: | Score | Signal | Action | |-------|--------|--------| | 80–100% | Healthy | Maintain, celebrate, document | | 65–79% | Warning | Identify specific friction — don't over-react | | 50–64% | Damaged | Urgent leadership attention + specific fixes | | < 50% | Crisis | Culture emergency — all-hands intervention |
Rituals are the delivery mechanism for culture. What works at 10 people breaks at 100.
Seed stage (< 15 people)
Early growth (15–50 people)
Scaling (50–200 people)
Large (200+ people)
Value-washing: Listing values you don't practice. Symptom: employees roll their eyes during values discussions.
Culture debt: Accumulating cultural compromises over time. "We'll address the toxic star performer later." Later compounds.
Founder culture trap: Culture stays frozen at founding team's personality. New hires assimilate or leave.
Culture by osmosis: Assuming culture transmits naturally. It did at 10 people. It doesn't at 50.
| When... | Culture Architect works with... | To... | | ------------------ | ------------------------------- | ----------------------------------------------------- | | Hiring surge | CHRO | Ensure culture fit is measured, not guessed | | Org reorg | COO + CEO | Manage culture disruption from structure change | | M&A or partnership | CEO + COO | Detect and resolve culture clashes early | | Performance issues | CHRO | Separate culture fit from skill deficit | | Strategy pivot | CEO | Update values/behaviors that the pivot makes obsolete | | Rapid growth | All | Scale rituals before culture dilutes |
references/culture-playbook.md — Netflix analysis, survey design, ritual examples, M&A playbooktemplates/culture-code-template.md — Culture code document templatetools
# ehAye Multimedia Use this skill for **video, audio, images, media conversion, previews, transcription, thumbnails, frame extraction, Spotter visual search, or FFmpeg-backed processing**. Core rule: use ehAye native media tools first. Do not reach first for shell `ffmpeg`, `ffprobe`, Python, or `mediainfo` when a native media tool can do the job. Native tools use bundled engines, show proper tool UI, respect cancellation/timeouts, integrate with Preview/Spotter, and avoid cross-platform shell
development
Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and Mocha. Use when the user asks to write tests, improve test coverage, practice TDD, generate mocks or stubs, or mentions testing frameworks like Jest, pytest, or JUnit. Handles test generation from source code, coverage report parsing (LCOV/JSON/XML), quality scoring, and framework conversion for TypeScript, JavaScript, Python, and Java projects.
tools
Help a user set up Telegram for ehAye Dojo. Default to Personal private bots (recommended). Group setup is advanced for teams/observers/demos.
development
# Writing Skills ## Overview **Writing skills IS Test-Driven Development applied to process documentation.** **Personal skills live in agent-specific directories (`~/.claude/skills` for Claude Code, `~/.agents/skills/` for Codex)** You write test cases (pressure scenarios with subagents), watch them fail (baseline behavior), write the skill (documentation), watch tests pass (agents comply), and refactor (close loopholes). **Core principle:** If you didn't watch an agent fail without the ski