data-consolidation-agent
Aggregates sales data into dashboards, generates territory breakdowns, tracks rep performance, and visualizes pipeline stages. Use when the user asks to build sales dashboards, generate pipeline or revenue reports, summarize sales performance by territory or rep, track quota attainment, analyze deal pipeline, review CRM data, or produce sales analytics and forecasts.
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 an excellent skill description that clearly articulates specific capabilities, provides comprehensive trigger terms covering the sales analytics domain, and explicitly states both what the skill does and when to use it. The description is well-structured, uses third person voice appropriately, and occupies a distinct niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: aggregates sales data into dashboards, generates territory breakdowns, tracks rep performance, and visualizes pipeline stages. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (aggregates sales data, generates territory breakdowns, tracks rep performance, visualizes pipeline stages) and 'when' with an explicit 'Use when...' clause listing multiple specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'sales dashboards', 'pipeline reports', 'revenue reports', 'sales performance', 'territory', 'rep', 'quota attainment', 'deal pipeline', 'CRM data', 'sales analytics', 'forecasts'. These are all terms a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche in sales-specific analytics and dashboards. The domain-specific terms like 'quota attainment', 'territory breakdowns', 'rep performance', 'CRM data', and 'pipeline stages' make it unlikely to conflict with general data analysis or other reporting skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with executable SQL queries, a clear multi-step workflow, and explicit validation checkpoints. Its main weakness is that it's somewhat lengthy for a single file—the full JSON schema and territory deep dive could be referenced separately. The content is well-organized and provides concrete, copy-paste-ready guidance throughout.
Suggestions
Consider moving the full JSON schema example to a separate SCHEMA.md file and keeping only a brief description in the main skill
Remove minor redundancy between Critical Rules and the workflow steps (e.g., attainment calculation is defined in both places)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable SQL and JSON examples, but includes some unnecessary verbosity like the full JSON schema example with sample data that could be more compact. The critical rules section restates things that are also covered in the workflow steps. | 2 / 3 |
Actionability | Provides fully executable SQL queries for each step, a complete JSON output schema with concrete example values, and specific calculation formulas (e.g., ytd_revenue / quota * 100). Every step is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 6-step sequential workflow with an explicit validation step (Step 5) that includes specific checks: cross-referencing per-rep and territory totals, flagging null quotas, and checking for empty pipelines. This is a well-structured feedback loop before final output. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and headers, but it's a fairly long monolithic file. The Territory Deep Dive section and potentially the full JSON schema could be split into referenced files. No external references are provided for advanced use cases. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- OpenRoster-ai/awesome-agents
- Commit
010799b
- 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.