expense-tracking-patterns
Patrones y l\u00f3gica de negocio para control de gastos basados en plantillas de Excel. Incluye categorizaci\u00f3n, f\u00f3rmulas, c\u00e1lculos financieros y detecci\u00f3n de gastos recurrentes. Usar cuando se trabaje con l\u00f3gica de transacciones, presupuestos o reportes financieros.
Install with Tessl CLI
npx tessl i github:iru97/Savvy-ai --skill expense-tracking-patterns79
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
92%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-crafted skill description that clearly articulates specific capabilities (categorization, formulas, financial calculations, recurring expense detection) and includes an explicit 'Use when' clause with relevant trigger terms. The description uses proper third-person voice and covers the expense control domain comprehensively. Minor weakness is potential overlap with other Excel or financial skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: categorization ('categorización'), formulas ('fórmulas'), financial calculations ('cálculos financieros'), and recurring expense detection ('detección de gastos recurrentes'). These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (expense control patterns, categorization, formulas, calculations, recurring expense detection) AND when ('Usar cuando se trabaje con lógica de transacciones, presupuestos o reportes financieros'). Has explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'gastos' (expenses), 'plantillas de Excel' (Excel templates), 'transacciones' (transactions), 'presupuestos' (budgets), 'reportes financieros' (financial reports). Good coverage of domain-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | While specific to expense control and Excel templates, there's potential overlap with general Excel skills or broader financial analysis skills. The Excel template focus helps distinguish it, but 'financial reports' and 'budgets' could trigger other financial skills. | 2 / 3 |
Total | 11 / 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 comprehensive, executable Dart code for expense tracking patterns with strong actionability. However, it's overly verbose with extensive inline category definitions that inflate token usage, and lacks clear workflow guidance for how to integrate these components. The content would benefit from better progressive disclosure by moving reference data to separate files.
Suggestions
Move the extensive default category definitions (gastosFixos, gastosVariables, ingresos) to a separate CATEGORIES.md reference file and summarize the structure in the main skill
Add a 'Quick Start' or 'Integration Workflow' section at the top showing the sequence of steps to implement expense tracking using these patterns
Consider splitting the VoiceCommandParser section into its own skill file given its distinct functionality and length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains extensive, well-structured code examples but includes some redundancy (e.g., full category definitions with colors/icons that could be summarized). The default categories section is particularly verbose and could be condensed or moved to a reference file. | 2 / 3 |
Actionability | Provides fully executable Dart code throughout with complete class definitions, methods, and concrete implementations. Code is copy-paste ready with clear data models, calculation functions, and parsing logic. | 3 / 3 |
Workflow Clarity | The skill presents individual components clearly but lacks explicit workflow sequences for how to use these patterns together. No validation checkpoints or step-by-step processes for implementing expense tracking - it's more of a reference library than a guided workflow. | 2 / 3 |
Progressive Disclosure | Content is organized into logical sections with clear headers, and includes one cross-reference to another skill file. However, the monolithic structure with 600+ lines of inline code could benefit from splitting detailed category definitions and parser patterns into separate reference files. | 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 (982 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.