CtrlK
BlogDocsLog inGet started
Tessl Logo

add-report

Guide for adding new report cards to ClaudeBar that analyze local data sources and display metrics with comparison deltas. Use this skill when: (1) Adding a new report/analytics card (e.g., weekly summary, model breakdown, session stats) (2) Creating data analysis features that read local files and display aggregated metrics (3) Adding comparison cards that show "today vs previous" style deltas (4) Building any feature that follows the DailyUsage pattern (parse → aggregate → report → card)

75

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable TDD workflow with clear sequencing, validation checkpoints, and a properly signaled one-level reference. The main weakness is mild verbosity from restating the workflow in multiple forms and some general Swift knowledge.

Suggestions

Collapse the ASCII data-flow diagram and the Phase-header list into a single representation to remove redundancy and trim the body.

Prune Key rules that restate general knowledge Claude already has (e.g., 'Use Decimal for monetary values (not Double — floating point errors)') and keep only project-specific conventions.

Move the full per-phase code templates into the existing reference file, leaving SKILL.md as a tighter overview pointing to the worked DailyUsage example.

DimensionReasoningScore

Conciseness

Mostly efficient and project-specific (e.g., 'Use Locale(identifier: "en_US") not en_US_POSIX which adds a space' is genuinely non-obvious), but the ~400-line body re-presents the workflow as both an ASCII flow diagram and again as Phase headers, and some Key rules restate general Swift knowledge Claude already has.

2 / 3

Actionability

Provides executable Swift patterns with exact file locations ('Sources/Domain/{Feature}/{Name}Stat.swift'), concrete commands ('tuist generate', 'xcodebuild test -scheme ...'), and copy-paste-ready templates; the {Name}/{Provider} placeholders are justified flexibility for a generic pattern skill.

3 / 3

Workflow Clarity

Phases 0–4 are explicitly sequenced with a mandatory approval gate in Phase 0, TDD red→green feedback loops in Phases 1–2, a dedicated verification phase with concrete test commands, and a per-phase checklist covering error recovery.

3 / 3

Progressive Disclosure

The body is a concise overview that signals a single one-level-deep reference in a blockquote ('See references/daily-usage-pattern.md for the complete DailyUsage feature'), and that referenced file exists and is not itself a chain of further references.

3 / 3

Total

11

/

12

Passed

Description

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.

The description is specific, complete, and well-triggered with a clear what-and-when structure in third-person voice. It carves out a distinct niche with natural trigger terms a user would actually say.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'adding new report/analytics card', 'Creating data analysis features that read local files', 'Adding comparison cards that show today vs previous style deltas', and 'Building any feature that follows the DailyUsage pattern'.

3 / 3

Completeness

Clearly answers both what ('Guide for adding new report cards to ClaudeBar that analyze local data sources and display metrics with comparison deltas') and when via an explicit 'Use this skill when:' clause with four enumerated triggers.

3 / 3

Trigger Term Quality

Good coverage of natural terms users would say — 'weekly summary', 'model breakdown', 'session stats', 'analytics card', 'today vs previous', 'comparison deltas' — matching the anchor's breadth.

3 / 3

Distinctiveness Conflict Risk

Narrow niche scoped to ClaudeBar report cards following the DailyUsage pattern, with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tddworks/ClaudeBar
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.