Track, manage, and get reminders for paid subscriptions and SaaS services. Use this skill whenever the user mentions subscriptions, SaaS costs, trial periods, recurring payments, billing cycles, or says things like "remind me about my subscription", "add a subscription", "how much do I spend on services", "when does my trial end", "track my subscriptions", or shares a service name/URL with a price. Triggers on any subscription-related intent even if the word "subscription" is not used — e.g. "I signed up for Notion Pro, $16/month, trial for 14 days". Also triggers when user asks about upcoming charges or trial expirations across any of their services.
94
Quality
94%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 hits all the marks. It provides specific capabilities, comprehensive trigger terms including natural user phrases and realistic examples, explicit 'Use when' guidance, and a clearly defined niche that distinguishes it from other skills. The inclusion of edge case handling (triggers even without the word 'subscription') demonstrates thoughtful design.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Track, manage, and get reminders for paid subscriptions and SaaS services.' The description clearly specifies the domain (subscriptions/SaaS) and actions (track, manage, reminders). | 3 / 3 |
Completeness | Clearly answers both what ('Track, manage, and get reminders for paid subscriptions and SaaS services') and when with explicit 'Use this skill whenever...' clause followed by comprehensive trigger scenarios including edge cases like when 'subscription' isn't explicitly mentioned. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'subscriptions', 'SaaS costs', 'trial periods', 'recurring payments', 'billing cycles', plus concrete example phrases like 'remind me about my subscription', 'how much do I spend on services', and even a realistic user input example with Notion Pro. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on subscription/SaaS tracking with distinct triggers around billing cycles, trial periods, and recurring payments. Unlikely to conflict with general finance or document skills due to specific subscription-focused language. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill with excellent conciseness and actionability. The content provides clear, specific guidance for all subscription management operations with concrete output examples. The only weakness is that workflow validation steps could be more explicit, particularly for operations that modify data.
Suggestions
Add explicit validation step after file writes (e.g., 'After saving, read back and confirm the subscription appears correctly')
Include a feedback loop for the delete operation: what to do if the subscription isn't found or if the file write fails
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and code blocks to convey information without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary explanations. | 3 / 3 |
Actionability | Provides concrete, executable guidance throughout: specific JSON schema, exact bash commands for date computation, clear table output formats, and precise rules for each operation. The confirmation prompts and edge case handling are specific and copy-paste ready. | 3 / 3 |
Workflow Clarity | Operations are clearly listed with good sequencing, but validation/confirmation steps are implicit rather than explicit checkpoints. For destructive operations like delete, there's a confirmation but no explicit feedback loop for error recovery. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections for each operation. Schema details are appropriately delegated to a separate reference file (references/schema.md), and the main content stays focused on operations and workflows. | 3 / 3 |
Total | 11 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Install with Tessl CLI
npx tessl i kiz8/subscription-tracker@0.1.0Reviewed
Table of Contents