frame-builder
Build in public with vibe raising. Launch your builder coin and ship products under it — every launch compounds funding and traction back to your builder. Claim vesting rewards and trading fees. Gas-free on Frame (Base).
62
Quality
52%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Critical
Do not install without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xnb-dev/openclaw-frame-builder-skills/SKILL.mdQuality
Discovery
32%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 reads more like marketing copy than a functional skill description, using buzzwords like 'vibe raising' and 'compounds funding and traction' without clearly explaining technical capabilities. It completely lacks explicit trigger guidance ('Use when...'), which is critical for skill selection. The crypto/web3 context is somewhat clear but could be more explicit with common user terminology.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'builder coin', 'token launch', 'Base chain', 'Frame', 'vesting rewards', or 'crypto creator economy'
Replace marketing language ('vibe raising', 'compounds funding') with concrete technical actions (e.g., 'Deploy ERC-20 tokens', 'Configure vesting schedules', 'Track trading fee distributions')
Include common user terminology variations like 'crypto', 'web3', 'token', 'blockchain', or 'smart contract' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names domain (builder coins, vesting rewards, trading fees) and some actions (launch, claim, ship products), but uses marketing language like 'vibe raising' and 'compounds funding' that obscures concrete technical capabilities. | 2 / 3 |
Completeness | Describes what it does (launch builder coins, claim rewards) but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'builder coin', 'vesting rewards', 'trading fees', 'Frame', 'Base', and 'gas-free', but missing common variations users might say like 'crypto', 'token launch', 'web3', or 'blockchain'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'builder coin' and 'Frame (Base)' terminology provides some distinctiveness, but 'build in public' and 'ship products' are generic enough to potentially conflict with general development or product launch skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
72%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-structured skill with strong actionability and excellent progressive disclosure through its reference documentation links. The main weaknesses are moderate verbosity (the OpenClaw integration and memory sections could be condensed or moved to references) and missing validation checkpoints for potentially risky operations like wallet creation and token launches.
Suggestions
Add explicit validation steps to the Quick Start workflow (e.g., 'Verify wallet created: node {baseDir}/src/balance.js' before proceeding to launch)
Move the OpenClaw Heartbeat Integration, Memory Integration, and Auto-Update sections to separate reference files to reduce the main skill length
Remove the Features bullet list since it duplicates the Commands table and Detailed Guides section
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundant sections (e.g., the OpenClaw integration details, memory integration, and auto-update sections add significant length). The features list at the top duplicates information found in the commands table. | 2 / 3 |
Actionability | Provides concrete, executable bash commands throughout with specific paths, flags, and examples. The command table is copy-paste ready, and troubleshooting includes direct solutions. | 3 / 3 |
Workflow Clarity | The Quick Start provides a clear sequence (1-4), but lacks explicit validation checkpoints. For operations involving wallet creation and token launches (potentially irreversible), there's no 'verify before proceeding' step or error recovery guidance in the main workflow. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise Quick Start, command reference table, and well-organized links to detailed guides in the references directory. All references are one level deep and clearly signaled with descriptive labels. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Repository
- Demerzels-lab/elsamultiskillagent
- Commit
45f9fac
- 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.