emblem-ai-react
React integration skill for EmblemAI's one-shot user management. Use when the user wants to add website authentication plus wallet-enabled users to a React app with EmblemAuthProvider, ConnectButton, social/email/wallet login, chat components, React auth hooks, React composition patterns, or Migrate.fun React hooks.
73
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/emblem-ai-react/SKILL.mdQuality
Discovery
89%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 a solid skill description that clearly identifies its niche (EmblemAI React integration) with explicit trigger guidance and product-specific terminology. Its main weakness is that it lists features/components rather than describing concrete actions the skill performs (e.g., 'configure', 'implement', 'integrate'). The strong trigger terms and explicit 'Use when' clause make it effective for skill selection.
Suggestions
Reframe the description to lead with concrete actions: e.g., 'Implements and configures EmblemAI authentication in React apps, including setting up EmblemAuthProvider, adding ConnectButton components, and integrating social/email/wallet login flows.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (React integration for EmblemAI user management) and lists several components/features (EmblemAuthProvider, ConnectButton, social/email/wallet login, chat components, React auth hooks), but doesn't describe concrete actions like 'configure', 'implement', or 'set up'. It reads more like a feature list than specific actions the skill performs. | 2 / 3 |
Completeness | The description clearly answers both 'what' (React integration for EmblemAI's one-shot user management) and 'when' with an explicit 'Use when...' clause listing multiple specific trigger scenarios including adding authentication, wallet-enabled users, and various React components/patterns. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'React app', 'authentication', 'wallet', 'EmblemAuthProvider', 'ConnectButton', 'social/email/wallet login', 'chat components', 'React auth hooks', 'Migrate.fun React hooks'. These are specific, natural terms a developer would use when seeking this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product names (EmblemAI, Migrate.fun) and the combination of React + authentication + wallet + specific component names (EmblemAuthProvider, ConnectButton). Very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions well as a routing/navigation document with excellent progressive disclosure to reference files, but it fails as a standalone skill because it contains zero executable code or concrete integration examples. The content is essentially a table of contents with marketing copy rather than actionable technical guidance. A user reading only this SKILL.md would not know how to write a single line of React code for EmblemAI integration.
Suggestions
Add a minimal but complete React code example in the Quick Start showing EmblemAuthProvider setup and a basic ConnectButton usage — this is critical for actionability.
Replace the 'What this gives a React app' marketing bullet list with a concrete code snippet showing provider composition (EmblemAuthProvider + HustleProvider wrapping an App component).
Add a brief workflow sequence for integrating EmblemAI into an existing React app: install dependencies → wrap app with providers → add auth components → verify login works.
Remove or significantly trim the Security & Trust Model section — the W011/W012 details are internal metadata that don't help Claude generate better React code.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably concise but includes some unnecessary filler. The 'What this gives a React app' section restates marketing-style benefits that don't add actionable value. The Security & Trust Model section, while potentially useful, is verbose for what it conveys. The 'In one sentence' line is redundant with the description. | 2 / 3 |
Actionability | The skill provides no executable code, no concrete React examples, no component usage patterns, and no copy-paste ready snippets. It only describes what exists and points to reference files. The 'Quick Start' is just an install command and example prompts, not actual integration guidance. | 1 / 3 |
Workflow Clarity | There is a basic two-step quick start (install, then ask), but no actual workflow for integrating EmblemAI into a React app. No sequenced steps for provider setup, component wiring, or configuration. For a React integration skill, the absence of a concrete setup workflow is a significant gap, though the simplicity of the 'install and ask' pattern partially mitigates this. | 2 / 3 |
Progressive Disclosure | The skill excels at progressive disclosure with a clean overview structure and well-signaled one-level-deep references to four specific reference files (auth-react.md, emblem-ai-react.md, react-components.md, migratefun-react.md). Related skills are also clearly linked. Navigation is straightforward. | 3 / 3 |
Total | 8 / 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.
- Repository
- EmblemCompany/Agent-skills
- Commit
2e138ef
- 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.