CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

arquiteto-de-empresa

Company Architect: builds a business from scratch as an OKF (Open Knowledge Format) bundle — a tree of version-controllable .md files with frontmatter type, links forming a graph, and reserved index.md/log.md, readable by humans and agents. Guides the founder through a 12-phase interview (foundation, strategy, market, financial, sales, marketing, product, operations, tech, people, legal, governance), one phase at a time, few questions per block, and generates the concepts as conformant markdown. Trigger when the user wants to create, structure, or document an entire company in folders and .md files; when they mention build my company from scratch, company as code, company knowledge base for AI to read, company wiki for agents, OKF, or knowledge bundle. In English.

76

Quality

95%

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

93%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.

An exemplary instruction-style skill body: lean, action-oriented, with a clearly sequenced multi-phase workflow and disciplined progressive disclosure backed by a complete, real bundle. The single gap is the missing explicit linter-failure recovery loop, which keeps workflow_clarity at 4.

Suggestions

Add one line after the linter command specifying the error-recovery loop, e.g. 'If okf_linter reports errors, fix the flagged concepts and re-run until it passes before regenerating the index.'

State what a linter failure looks like or the most common failure modes (missing type, broken link) so recovery is actionable without reading the script.

Clarify the fallback path when disk access is unavailable mid-phase (principle 10 covers writing files without disk, but the per-phase loop in step (d) does not mention it).

DimensionReasoningScore

Conciseness

The ~80-line body is dense and directive with no filler: conformance rules are compressed to 5 numbered lines with detail delegated to references, principles are one line each, and commands are shown once. The only explanation of an unknown concept (OKF) is necessary, since it is a custom format Claude would not know. Not level 4 because no section is padded or restated beyond the deliberate one-line summary-plus-reference pattern.

5 / 5

Actionability

Fully executable guidance: copy-paste bash invocations for all three scripts with realistic flags ('python scripts/scaffold_bundle.py "My Company" --out ./my-company --has-product --has-tech'), a concrete link syntax example ('[Identity](../00-fundacao/identidade.md)'), a recommended flow, and a numbered 'How to start' procedure. Not level 4 because the common cases (scaffold, per-phase loop, validation, index regeneration) are each covered by specific, runnable commands or explicit steps.

5 / 5

Workflow Clarity

The sequence is clear with most checkpoints present: interview-before-build gating, 'Stop and wait' for answers, 'Confirm before generating... ask for ok', and an explicit okf_linter validation step after each phase. Not level 5 because the error-recovery loop is incomplete — the body says to run okf_linter but never states what to do on linter failure (fix and re-run), leaving that feedback loop implicit. Not level 3 because validation checkpoints are explicit and repeated per phase, not merely implicit.

4 / 5

Progressive Disclosure

SKILL.md is a clean overview with well-signaled, one-level-deep references: 3 reference files, 4 assets, and 3 scripts, all verified to exist, each linked inline with a one-line description of its purpose and enumerated again in a References/Assets section. Reference files link only to siblings, so no nested read chains. Not level 4 because there is no content that should have been split out still inlined, and every navigation path is explicit.

5 / 5

Total

19

/

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: third-person voice, explicit what/when, concrete artifact definition, and a rich set of natural trigger phrases including synonyms. The only weakness is slight trigger overlap with generic knowledge-base/wiki skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with comprehensive coverage: 'builds a business from scratch as an OKF bundle', 'Guides the founder through a 12-phase interview', 'generates the concepts as conformant markdown', and specifies the output artifact precisely ('a tree of version-controllable .md files with frontmatter type, links forming a graph, and reserved index.md/log.md'). Not level 4 because coverage is comprehensive, not just 'several specific actions with minor gaps' — what is produced, how (12-phase interview), and the artifact format are all explicit.

5 / 5

Completeness

Both 'what' (builds a business as an OKF bundle; 12-phase interview; generates conformant markdown) and 'when' are explicitly answered with a literal trigger clause ('Trigger when the user wants to create, structure, or document an entire company...'). Matches the level-5 anchor of explicit what AND when with concrete trigger phrases; level 4 would require a weaker or less specific 'when'.

5 / 5

Trigger Term Quality

Natural trigger phrases include 'build my company from scratch', 'company as code', 'company knowledge base for AI to read', 'company wiki for agents', 'OKF', 'knowledge bundle', plus 'create, structure, or document an entire company in folders and .md files' — covering synonyms and file-format terms a user would naturally say. Not level 4 because the term set is comprehensive rather than missing 'a few natural terms'.

5 / 5

Distinctiveness Conflict Risk

The niche (entire-company-as-code OKF bundle) is mostly distinct with triggers like 'company as code' and 'OKF'. Not level 5 because 'company wiki for agents' and 'knowledge bundle' carry minor overlap risk with generic documentation/wiki-building skills that could claim the same trigger. Not level 3 because the overlap is narrow and the core triggers ('build my company from scratch', OKF) are unmistakable for this skill.

4 / 5

Total

19

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

c-level-advisor/arquiteto-de-empresa/skills/arquiteto-de-empresa/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.