CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

project-organization

Regras para organização de projetos em config/ vs logs/ - quando usar cada pasta

Quality

65%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/workflow/project-organization/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 delivers concrete, actionable rules with exact paths, a required structure, and a deterministic decision checklist — well suited to an instruction-only skill. Its weaknesses are repetition of the core rule across four sections and a move workflow lacking a validation checkpoint for a batch/restructuring operation. Overall solid, with tightening and a verification step as the main uplifts.

Suggestions

Add an explicit validation checkpoint to the move workflow (e.g. a final step: verify the standard structure was applied, README.md exists, and no permanent context remains in logs/) — the workflow_clarity cap of 3 for batch operations without validation applies.

Merge the 'Checklist de Decisão' and 'Importante' sections into the criteria sections, or replace them with a one-line pointer — both are near-verbatim repeats of the ✅/❌ criteria and the 'Objetivo' statement.

Clarify move step 4: state explicitly whether 'historico-contexto' is copied from logs/ or left in place, and where it lives relative to the moved project.

DimensionReasoningScore

Conciseness

Mostly efficient — no filler explaining concepts Claude already knows — but the single core rule (approved → config/, otherwise → logs/) is restated four times across the 'Critérios', 'Checklist de Decisão', 'Exemplos', and 'Importante' sections (e.g. 'NUNCA acumular contexto permanente' repeats 'Evitar acumular contexto permanente'), so it could be tightened. Not 2 because each restatement serves a distinct function (criteria, decision checklist, worked examples) rather than being pure padding; not 4 because the checklist and 'Importante' sections are near-verbatim repeats that could be merged with real information loss of near zero.

3 / 5

Actionability

Concrete, executable guidance throughout: exact paths ('config/work/freelancer/[projeto]/'), a full required directory structure, a deterministic decision rule ('Se TODAS as respostas forem SIM → config/'), and a 4-step move procedure. Not 5 because step 4 of the move ('Manter histórico relevante em logs/work/[projeto]/historico-contexto/') is ambiguous about whether history is copied or moved and no command/path is given for the move itself; not 3 because the guidance goes well beyond pseudocode-level hints and the examples cover the common cases.

4 / 5

Workflow Clarity

The 'Quando Mover de Logs para Config' sequence lists 4 ordered steps and the decision checklist gives explicit branching, but the move workflow is a batch/restructuring operation with no validation checkpoint (nothing verifies the structure was applied, the README created, or no permanent context left behind). Per the rubric's cap, a batch/destructive workflow without validation cannot score above 3. Not 2 because the sequence is well defined with no gaps; not 4+ because checkpoints are entirely implicit.

3 / 5

Progressive Disclosure

No bundle files exist, and the single-file body is well organized with clear hierarchical sections (critical rule, move procedure, checklist, general rule, examples) that are easy to navigate. Not 5 because the skill exceeds 50 lines, so the simple-skill exception does not strictly apply, and the repeated criteria/examples content could live in a separate reference file or be cut; not 3 because the structure is good and nothing that clearly belongs in a separate file is buried.

4 / 5

Total

14

/

20

Passed

Description

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

The description carves out a distinct, specific niche (config/ vs logs/ project organization) in third-person voice, but it is thin as an invocation surface: it lists only one action, keeps natural trigger terms in a separate frontmatter field instead of the description, and lacks any 'Use when...' trigger clause. It is serviceable but sits just above the midpoint of the rubric.

Suggestions

Add an explicit trigger clause, e.g. 'Use quando criar, mover ou organizar projetos, propostas ou pastas de trabalho, ou ao decidir entre config/ e logs/.' — this directly lifts completeness.

Fold the natural trigger terms currently stranded in the frontmatter triggers field (organizar, mover, estrutura, proposta, freelancer) into the description text itself to improve trigger-term coverage.

Name the concrete actions the skill performs (e.g. 'move projetos aprovados de logs/ para config/, aplica a estrutura padrão de pastas') to raise specificity beyond one action.

DimensionReasoningScore

Specificity

'Regras para organização de projetos em config/ vs logs/ - quando usar cada pasta' names the domain (organizing projects across two named folders) and essentially one action (deciding when to use each folder). It matches 'Names domain and 1-2 concrete actions, but not comprehensive'. Not 4 because it does not list several specific actions the skill actually performs (mover projetos aprovados, aplicar estrutura padrão, criar README); not 2 because it is far more concrete than generic filler like 'Helps with documents'.

3 / 5

Completeness

The 'what' is clear (rules for organizing projects between config/ and logs/), and 'quando usar cada pasta' names the topic, but there is no 'Use when...' clause or equivalent explicit invocation guidance — the phrase describes the skill's subject matter, not when Claude should load it. Per the rubric guideline, a missing 'Use when...' clause caps completeness at 3. Not 4 because an explicit trigger clause is absent; not 2 because the 'what' is fully stated and a 'when' topic is at least weakly present.

3 / 5

Trigger Term Quality

The description contains some natural, relevant keywords ('organização de projetos', 'config/', 'logs/') but misses common variations and synonyms ('estrutura', 'pasta', 'mover', 'proposta', 'freelancer') that only appear in the separate frontmatter triggers field, not the description itself. This matches 'Some relevant keywords but missing common variations or synonyms'. Not 4 because coverage within the description text itself is thin; not 2 because the terms present are specific and natural, not generic.

3 / 5

Distinctiveness Conflict Risk

The config/ vs logs/ folder taxonomy with 'projetos' is a personal, well-defined niche that few other skills would claim — 'clear niche with distinct triggers' territory. Not 5 because 'organização de projetos' could still overlap with generic project-management or file-organization skills; not 3 because the named folders make it substantially more distinct than a 'Works with X files' level of specificity.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

fernandezbaptiste/cursor-multiagent-system

Path

skills/workflow/project-organization/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.