bun-macros

Evaluate JavaScript at bundle time and inline results. Use when optimizing compile-time code generation, embedding files, inlining environment variables, or executing code during the bundling process.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

75%Weight 40%Scale 1-5

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

The body is highly actionable with complete executable examples and clear section organization, and it appropriately signals progressive disclosure via a dedicated reference-loading section. It loses points on workflow clarity (no explicit validate/retry loop for build failures) and slightly on conciseness due to repetitive import patterns.

Suggestions

Add a short validate/fix/retry feedback loop for build failures — e.g., after `bun build`, run the build again or check the macro output to confirm inlining succeeded before proceeding.

Create the referenced files (references/advanced-patterns.md and references/debugging.md) so the progressive-disclosure pointers resolve to real bundle files.

Consolidate the repeated `import { ... } from "./macros/*" with { type: "macro" }` boilerplate, which appears nearly verbatim in many sections, into a single explained pattern.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient, relying on annotated code blocks rather than prose explanation and assuming Claude's competence, but a few sections (e.g. 'Macros ONLY run during bundling', some near-duplicate import patterns across many use cases) could be tightened.	4 / 5
Actionability	Almost every section provides complete, copy-paste-ready, executable TypeScript along with concrete build commands, covering the common cases (env inlining, git info, file embedding, codegen) with specific examples.	5 / 5
Workflow Clarity	The skill is effectively single-purpose (write a macro, import with the macro attribute, run bun build) so it does not need a multi-step workflow, but there are no explicit validation checkpoints for build failures — the 'Error Handling' and 'Common Errors' sections describe failure modes without a validate/fix/retry feedback loop.	3 / 5
Progressive Disclosure	The body is well-sectioned and ends with a clearly signaled 'When to Load References' section pointing to two one-level-deep reference files (advanced-patterns.md, debugging.md), but the listed reference files do not actually exist in the bundle, so navigation is signaled but not fully backed by real files.	4 / 5
	Total	16 / 20 Passed

Description

86%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, well-targeted description that clearly states what the skill does and when to use it, with concrete trigger phrases. Minor gains are possible by tightening the slightly redundant final clause and adding a few more natural synonyms.

Dimension	Reasoning	Score
Specificity	The description names several concrete actions ('Evaluate JavaScript at bundle time and inline results') and lists specific use cases (optimizing compile-time code generation, embedding files, inlining environment variables), but 'executing code during the bundling process' is somewhat redundant rather than a distinct new action.	4 / 5
Completeness	It explicitly answers both 'what' ('Evaluate JavaScript at bundle time and inline results') and 'when' ('Use when optimizing compile-time code generation, embedding files, inlining environment variables, or executing code during the bundling process') with concrete trigger phrases.	5 / 5
Trigger Term Quality	It includes natural trigger phrases users would say ('optimizing compile-time code generation', 'embedding files', 'inlining environment variables'), but is missing common synonyms/variations like 'build-time code', 'bundle-time macros', or file extensions; coverage is good but not comprehensive.	4 / 5
Distinctiveness Conflict Risk	The niche is narrow and clearly scoped to Bun bundle-time macros, with distinct triggers ('bundle time', 'compile-time code generation') that make it unlikely to fire for unrelated skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: secondsky/claude-skills
Path: plugins/bun/skills/bun-macros/SKILL.md
Commit: ad16332

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

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.