financial-insights
Patrones para generar insights financieros inteligentes y sugerencias de ahorro contextuales. Incluye clasificación de gastos evitables vs necesarios, detección de oportunidades de ahorro, y mensajes personalizados. Usar cuando se trabaje con recomendaciones al usuario o análisis de hábitos de gasto.
74
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
77%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 is a well-structured description that clearly explains what the skill does and when to use it. The specificity of capabilities is strong with concrete actions listed. However, trigger term coverage could be expanded to include more natural user language variations, and the distinctiveness could be improved by narrowing the scope of when-triggers.
Suggestions
Expand trigger terms to include common user phrases like 'presupuesto', 'ahorrar dinero', 'finanzas personales', 'gastos mensuales'
Make the 'when' clause more distinctive by specifying unique scenarios like 'when analyzing spending patterns for savings opportunities' rather than the generic 'recomendaciones al usuario'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'clasificación de gastos evitables vs necesarios', 'detección de oportunidades de ahorro', 'mensajes personalizados', and 'generar insights financieros inteligentes'. | 3 / 3 |
Completeness | Clearly answers both what (patterns for financial insights, expense classification, savings detection, personalized messages) AND when ('Usar cuando se trabaje con recomendaciones al usuario o análisis de hábitos de gasto'). | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'ahorro', 'gastos', 'recomendaciones', 'hábitos de gasto', but missing common variations users might say like 'presupuesto', 'dinero', 'finanzas personales', 'ahorrar dinero'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to financial insights and savings, but could overlap with general financial analysis skills or budgeting tools. The focus on 'gastos evitables vs necesarios' adds some distinction but 'recomendaciones al usuario' is quite broad. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, executable Dart code for generating financial insights with a well-thought-out reducibility classification system. The main weaknesses are the monolithic structure that could benefit from splitting into multiple files, and the lack of explicit validation workflows for ensuring generated insights are contextually appropriate before display.
Suggestions
Split the reducibility matrix, InsightGenerator class, and UI components into separate referenced files (e.g., REDUCIBILITY.md, GENERATOR.md, UI_COMPONENTS.md) to improve progressive disclosure
Add a validation workflow section that explicitly checks generated insights against user context before displaying (e.g., verify seasonal context, check for recent life changes)
Remove obvious implementation notes like 'Nunca ser condescendiente' and 'Respetar privacidad' that Claude inherently understands
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is comprehensive but includes some redundancy. The extensive Dart code examples are useful but could be more condensed. Some explanatory text (like the 'Notas de Implementación' section) states obvious principles Claude would already understand. | 2 / 3 |
Actionability | Provides fully executable Dart code with complete class definitions, enums, and methods. The reducibility matrix, insight generator, and UI widget are copy-paste ready. JSON examples show exact expected outputs. | 3 / 3 |
Workflow Clarity | The insight generation process is well-structured with clear steps (analyze subcategories, compare with previous, detect unusual spending, etc.), but lacks explicit validation checkpoints. No feedback loops for error handling or verification that generated insights are appropriate before showing to users. | 2 / 3 |
Progressive Disclosure | Content is organized into logical sections with clear headers, but everything is in a single monolithic file. The extensive code examples (400+ lines) could be split into separate reference files for the reducibility matrix, insight generator, and UI components. | 2 / 3 |
Total | 9 / 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 (503 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 | |
- 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.