Advogado especialista em todas as areas do Direito brasileiro: familia, criminal, trabalhista, tributario, consumidor, imobiliario, empresarial, civil e constitucional.
38
Quality
24%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/advogado-especialista/SKILL.mdQuality
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description identifies a domain (Brazilian law) and lists practice areas but fails to specify concrete actions the skill performs or when Claude should use it. It reads more like a professional bio than a functional skill description, lacking the actionable specificity and trigger guidance needed for effective skill selection.
Suggestions
Add concrete actions the skill performs, e.g., 'Redige petições, analisa contratos, interpreta legislação, orienta sobre direitos e deveres'
Include a 'Use when...' clause with explicit triggers, e.g., 'Use quando o usuário mencionar questões legais, contratos, processos judiciais, ou pedir orientação jurídica no contexto brasileiro'
Add natural user trigger terms like 'advogado', 'lei', 'contrato', 'processo', 'direitos', 'petição' that users would actually say when needing legal help
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states expertise areas ('familia, criminal, trabalhista...') but lists no concrete actions. It describes what the skill 'is' (a specialist) rather than what it 'does' (e.g., 'drafts petitions', 'analyzes contracts', 'reviews legal documents'). | 1 / 3 |
Completeness | The description only partially addresses 'what' (legal expertise areas) and completely lacks a 'when' clause. There is no 'Use when...' guidance or explicit trigger conditions for Claude to know when to select this skill. | 1 / 3 |
Trigger Term Quality | Contains domain-specific Portuguese legal terms (familia, criminal, trabalhista, tributario, consumidor, imobiliario, empresarial, civil, constitucional) that users might mention, but lacks action-oriented trigger terms users would naturally say like 'contrato', 'petição', 'processo', 'advogado', 'lei'. | 2 / 3 |
Distinctiveness Conflict Risk | The Brazilian law focus provides some distinctiveness, but claiming expertise in 'todas as areas' (all areas) is overly broad and could conflict with more specialized legal skills. The lack of specific use cases increases overlap risk. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an exhaustive legal reference document that treats Claude as if it needs to learn Brazilian law from scratch. While comprehensive, it violates token efficiency by including encyclopedic content that should be in separate reference files or assumed as Claude's existing knowledge. The 12-step workflow provides some structure but the overall document is far too verbose for a skill file.
Suggestions
Split the 14 legal modules into separate reference files (e.g., FAMILIA.md, CRIMINAL.md, TRABALHISTA.md) and keep SKILL.md as a concise routing overview under 200 lines
Remove explanatory content about basic legal concepts (what divorce is, what damages are) and focus only on Brazil-specific procedures, thresholds, and decision trees Claude wouldn't know
Add explicit validation steps to the 12-step workflow (e.g., 'Verify prescription deadline before proceeding', 'Confirm jurisdiction before filing')
Convert verbose tables into decision trees or flowcharts that guide action rather than serve as encyclopedic reference
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 1000+ lines with extensive tables explaining basic legal concepts Claude already knows (what divorce is, types of damages, etc.). Much of this is encyclopedic reference material that could be condensed or linked externally. | 1 / 3 |
Actionability | Provides structured tables and a 12-step workflow template which are somewhat actionable, but lacks executable code examples and specific commands. The guidance is more reference-oriented than step-by-step actionable instructions. | 2 / 3 |
Workflow Clarity | The 12-step workflow is clearly sequenced but lacks explicit validation checkpoints or feedback loops. The module routing table (Módulo 1-14) provides structure but doesn't explain how to validate decisions or handle errors in analysis. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with all 14 modules inline rather than split into separate files. References to external skills (advogado-criminal) exist but the main content is not appropriately distributed. Over 1000 lines in a single file violates progressive disclosure principles. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (1110 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
8692fbc
Table of Contents
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.