jbaruch/frequent-flyer-advocate
Write professional, persuasive complaint letters to US airlines emphasizing loyalty status, DOT regulations, and airline commitments.
Overall
score
92%
Does it follow best practices?
Validation for skill structure
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 exemplary skill description that excels across all dimensions. It provides specific capabilities (complaint letter writing with emphasis on loyalty status and regulations), comprehensive trigger terms covering both user intents and specific scenarios, and a clear 'Use when:' clause. The narrow focus on US airline complaints makes it highly distinctive and unlikely to conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Write professional, persuasive complaint letters', 'request compensation', 'dispute an airline's response', 'escalate an airline issue', 'file a DOT complaint'. Also specifies the approach: 'Emphasizes loyalty status, DOT regulations, and the airline's own published commitments.' | 3 / 3 |
Completeness | Clearly answers both what (write complaint letters emphasizing loyalty, DOT regulations, airline commitments) AND when (explicit 'Use when:' clause with comprehensive trigger scenarios covering both user intents and specific airline service failures). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'complain to an airline', 'complaint letter', 'compensation', 'DOT complaint', 'bad flight experience', plus specific scenarios like 'flight delay', 'cancellation', 'lost baggage', 'denied boarding', 'downgrade', 'missed connection'. These are exactly the phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: specifically US airlines, complaint letters, DOT regulations. The combination of 'airline' + 'complaint/compensation' + specific failure types creates a clear, non-conflicting trigger profile that wouldn't overlap with general writing or other travel skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%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 workflow clarity and progressive disclosure. The 5-phase structure with explicit gates prevents premature action, and the reference file organization is ideal. Minor verbosity in explanatory passages (why certain approaches work) could be trimmed to improve token efficiency.
Suggestions
Trim explanatory rationale (e.g., 'Quoting the airline's own words back to them is what makes the letter powerful') - Claude understands persuasion strategy without being told why it works.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is well-organized but includes some unnecessary explanation (e.g., explaining why quoting airline's own words is powerful, general advice about professional tone). Some sections could be tightened while preserving clarity. | 2 / 3 |
Actionability | Provides highly concrete guidance: specific questions to ask, exact letter structure with examples, specific timelines (14-21 days, 30 days), exact DOT website, and clear install command for Playwright. The referenced files contain additional executable details. | 3 / 3 |
Workflow Clarity | Excellent 5-phase workflow with explicit gates (don't proceed to research until flight verified, don't proceed to writing until 6+ research items gathered). Clear validation checkpoints and decision points throughout. | 3 / 3 |
Progressive Disclosure | Exemplary structure: main skill provides the workflow overview while detailed procedures (flight verification, research strategy, compensation tiers) are appropriately split into one-level-deep reference files with clear signaling. | 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 jbaruch/frequent-flyer-advocate@0.1.0Reviewed
Table of Contents