antfu-coding-style
Opinionated coding style and tooling preferences by Anthony Fu.
56
Quality
38%
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
0%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 critically underdeveloped. It provides no concrete actions, no trigger terms users would naturally use, and no guidance on when to apply the skill. The reference to 'Anthony Fu' assumes knowledge the user may not have, and the vague 'coding style and tooling preferences' language would cause conflicts with many other potential skills.
Suggestions
Add specific actions the skill performs, e.g., 'Configures ESLint, Prettier, and TypeScript with opinionated defaults. Sets up Vue/Vite projects with specific conventions.'
Add a 'Use when...' clause with trigger terms like 'antfu config', 'eslint-config-antfu', '@antfu/eslint-config', 'Vue project setup', or 'opinionated linting'.
Include the specific tools and frameworks this style applies to (e.g., Vue, Vite, TypeScript, ESLint) to distinguish it from generic coding style skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only 'coding style and tooling preferences' which is abstract. It doesn't specify what actions Claude should take (e.g., format code, configure tools, apply linting rules). | 1 / 3 |
Completeness | Missing both 'what' and 'when'. The description doesn't explain what specific actions the skill performs, nor does it provide any guidance on when Claude should use it. No 'Use when...' clause or equivalent. | 1 / 3 |
Trigger Term Quality | No natural keywords users would say. 'Anthony Fu' is a proper noun that most users wouldn't mention unless they specifically know this person. 'Coding style' and 'tooling preferences' are vague and don't include specific terms like 'ESLint', 'Prettier', 'TypeScript config', etc. | 1 / 3 |
Distinctiveness Conflict Risk | 'Coding style and tooling preferences' is extremely generic and would conflict with any other code formatting, linting, or configuration skills. Nothing distinguishes this from general coding assistance. | 1 / 3 |
Total | 4 / 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 well-crafted, concise style guide that efficiently communicates Anthony Fu's coding preferences. It excels at token efficiency and clear organization but could improve actionability with more executable code examples and progressive disclosure with links to detailed resources for each tool mentioned.
Suggestions
Add executable code snippets for Vitest setup and UnoCSS configuration to improve actionability
Include links to official documentation or example repos for tools like UnoCSS, Vitest, and ni for progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses bullet points, minimal prose, and assumes Claude understands TypeScript, Vue, and tooling concepts. Every line adds value without explaining basics. | 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 illustrative than copy-paste ready. | 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 for each domain (TypeScript, tooling, CSS, Vue). | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections and hierarchy, but could benefit from references to external resources (e.g., UnoCSS docs, Vitest setup guides) for deeper exploration. All content is inline. | 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
- Dokhacgiakhoa/antigravity-ide
- Commit
3395991
- 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.