antfu-coding-style
Opinionated coding style and tooling preferences by Anthony Fu.
56
46%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/skills/antfu-coding-style/SKILL.mdQuality
Discovery
7%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 description is severely lacking in actionable detail. It fails to specify what concrete actions the skill performs, provides no natural trigger terms users would say, and lacks any 'Use when...' guidance. The only distinguishing element is the attribution to Anthony Fu, but without knowing what tools or styles this encompasses, Claude cannot effectively select this skill.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Configures ESLint, Prettier, and TypeScript settings according to Anthony Fu's style guide').
Include a 'Use when...' clause with natural trigger terms (e.g., 'Use when setting up linting, code formatting, or when the user mentions @antfu, eslint-config, or Anthony Fu's coding conventions').
List the specific tools, configurations, or file types this skill handles to improve trigger term quality and distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Opinionated coding style and tooling preferences' is entirely abstract with no indication of what the skill actually does (e.g., formats code, configures linters, applies style rules). | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no 'Use when...' clause and no explicit triggers. It only vaguely references whose preferences these are, not what actions the skill performs. | 1 / 3 |
Trigger Term Quality | The only potentially useful trigger is 'Anthony Fu' (a specific person), but 'coding style' and 'tooling preferences' are overly generic. Users would more likely say specific terms like 'ESLint', 'Prettier', 'formatting', or name specific tools Anthony Fu is known for. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Anthony Fu' provides some distinctiveness as it references a specific person's preferences. However, 'coding style and tooling preferences' is generic enough to potentially conflict with other code formatting or linting skills. | 2 / 3 |
Total | 5 / 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, concise style guide that respects token budget while providing clear, opinionated guidance. The content is appropriately structured for its purpose as a coding philosophy reference. Minor weakness is that some sections could benefit from more executable examples rather than just good/bad comparisons.
Suggestions
Add a complete executable code example for the testing section showing a Vitest test with toMatchInlineSnapshot()
Include a small but complete Vue component example demonstrating the preferred script setup structure with defineProps/defineEmits positioning
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses bullet points, minimal prose, and concrete examples. No unnecessary explanations of concepts Claude already knows. Every line adds value. | 3 / 3 |
Actionability | Provides concrete examples (good/bad TypeScript patterns, UnoCSS syntax, ni commands) but lacks executable code blocks. The guidance is specific but more prescriptive than executable - it tells you what to prefer rather than showing complete working examples. | 2 / 3 |
Workflow Clarity | This is a style/philosophy skill, not a multi-step process skill. The single-purpose guidance is unambiguous with clear preferences stated. No destructive operations requiring validation checkpoints. | 3 / 3 |
Progressive Disclosure | For a sub-50-line style guide, the content is well-organized into logical sections (Code Organization, TypeScript, Tooling, CSS, Vue). No need for external references given the scope. Clear headers enable easy navigation. | 3 / 3 |
Total | 11 / 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
- Dokhacgiakhoa/antigravity-ide
- Commit
332e58b
- 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.