CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

emojis-rules

Regras sobre uso de emojis em código e documentação

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/emojis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 a clear, concrete, and appropriately brief set of emoji-prohibition rules with a pre-commit validation checklist. Its main weaknesses are redundant restatement of the same rules across sections, an unspecified detection method for validation, no criterion for classifying work vs. study projects, and references to files that are not part of the bundle.

Suggestions

Add a concrete detection method to the validation section, e.g., a grep/regex command for emoji ranges (such as grep -P '[\x{1F300}-\x{1FAFF}]') so the pre-commit checks are executable.

Merge 'Regras por Tipo de Projeto' into the general rules as a single exceptions table, since the work/study subsections repeat the same prohibitions and permissions verbatim.

State how to classify a project (e.g., a marker file, repo ownership, or ask the user) and either remove the references to core/agents/programming.mdc and core/templates/ or include those files in the bundle.

DimensionReasoningScore

Conciseness

The body is mostly lean rule lists, but 'Regras por Tipo de Projeto' restates the general prohibition and the same exceptions nearly verbatim — the same rules appear three times across sections. This fits 'Mostly efficient but includes some unnecessary explanation or could be tightened'; not 2, since there is no concept-explanation padding, only restatement.

3 / 5

Actionability

As an instruction-only skill the guidance is concrete: enumerated file types ('.toml, .ini, .yaml, .yml, .json, .env'), explicit exceptions ('README.md', 'notebooks Jupyter (.ipynb)'), and per-project-type rules. The minor gap is the validation checklist ('Verificar se há emojis em código') which provides no detection method such as a grep or regex command — matching 'Mostly executable guidance... with minor gaps'.

4 / 5

Workflow Clarity

This is a simple single-action rule skill with a pre-commit validation checklist, and the single action is largely unambiguous, but how to determine whether a project is 'Trabalho/Work' or 'Estudos' is never stated, leaving a real decision point implicit. That places it at 'clear guidance with minor gaps' rather than 5.

4 / 5

Progressive Disclosure

Sections are well organized and the content is appropriately inline for a skill of this size with no bundle files. The gap is the 'Referências' section pointing to 'core/agents/programming.mdc' and 'core/templates/', which do not exist in this skill's bundle — dangling references with no explanation of their contents, fitting 'Good structure... minor organization gaps' rather than 5.

4 / 5

Total

15

/

20

Passed

Description

48%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 correctly names its niche (emoji usage rules for code and documentation) in third person, but it is minimal: it states no concrete actions, no 'when to use' guidance, and only one distinctive trigger term. It reads more as a title than an operational description.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g., 'Use quando o usuário mencionar emojis, unicode, símbolos ou ícones em código, commits ou documentação.'

State what the skill actually does, not just its topic — e.g., 'Define e aplica regras que proíbem emojis em código, commits e arquivos de configuração, permitindo-os apenas em README.md e notebooks Jupyter.'

Include natural trigger variations (emoji, emojis, unicode, symbols, ícone) that already exist in the frontmatter triggers field directly in the description text.

DimensionReasoningScore

Specificity

"Regras sobre uso de emojis em código e documentação" names the domain (emoji usage in code and documentation) but lists zero concrete actions, matching the anchor 'Names the domain but actions are minimal or generic'. It is not 3 because no concrete action (e.g., verifying, prohibiting, validating) is stated, and not 1 because the domain is clearly identified.

2 / 5

Completeness

The 'what' is stated (rules governing emoji usage in code and documentation) but there is no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the judging guidelines. Score 4 is excluded because no 'when' guidance appears in the description text.

3 / 5

Trigger Term Quality

"emojis" is a natural term users would say, with "código" and "documentação" as generic domain words, but common variations and synonyms (unicode, symbols, ícone) are missing from the description. This fits 'Some relevant keywords but missing common variations or synonyms' rather than 4, since only one distinctive natural term is present.

3 / 5

Distinctiveness Conflict Risk

Emoji governance is a clear niche that a user mentioning emojis would naturally route to, with only minor overlap risk against general coding-style or linting skills — matching 'Mostly distinct; minor overlap risk'. Not 5, since the anchor-5 example includes concrete trigger phrases that this description lacks.

4 / 5

Total

12

/

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/emojis/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.