1Forge integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1Forge data.
52
41%
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 ./skills/1forge/SKILL.mdQuality
Discovery
17%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 fails to explain what 1Forge actually is (a forex/currency data API) and uses generic language that could apply to almost any data integration. The lack of domain-specific keywords means users asking about currency exchange rates or forex data would never trigger this skill. The description assumes users already know what 1Forge is rather than describing its actual capabilities.
Suggestions
Explain what 1Forge is and list specific capabilities: 'Access real-time forex rates, convert currencies, retrieve market quotes from 1Forge API'
Add natural trigger terms users would say: 'Use when the user asks about currency exchange rates, forex data, currency conversion, or real-time market quotes'
Remove generic phrases like 'manage data, records, and automate workflows' and replace with concrete forex-related actions
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Manage data, records, and automate workflows' without specifying concrete actions. It doesn't explain what 1Forge actually does (forex/currency data) or what specific operations are available. | 1 / 3 |
Completeness | Has a 'Use when...' clause which addresses the 'when' question, but the 'what' is extremely vague. The trigger condition '1Forge data' is too narrow and assumes prior knowledge of the service. | 2 / 3 |
Trigger Term Quality | The only trigger term is '1Forge data' which assumes users already know what 1Forge is. Missing natural keywords users would say like 'forex', 'currency', 'exchange rates', 'financial data', or 'market quotes'. | 1 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is extremely generic and could apply to dozens of integration skills. Only '1Forge' provides distinctiveness, but without explaining what 1Forge is, it fails to differentiate from other data management tools. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable CLI commands for integrating with 1Forge via Membrane, with good coverage of connection setup, action discovery, and proxy requests. However, it wastes tokens explaining what 1Forge and forex data are, includes a confusing overview section, and lacks validation steps for the multi-step connection workflow.
Suggestions
Remove the opening paragraph explaining what 1Forge is - Claude already knows this and can infer it from context
Either expand the '1Forge Overview' section to be useful (explaining what each capability does) or remove it entirely
Add validation checkpoints to the connection workflow, e.g., 'Verify connection succeeded: membrane connection list --json | grep CONNECTION_ID'
Add error handling guidance for common failure cases (auth failures, invalid connection IDs, rate limits)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what 1Forge is and what forex data is used for - information Claude already knows. The CLI setup and best practices sections are reasonably efficient, but there's unnecessary explanation throughout. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, including JSON parameter passing, proxy requests with flag documentation, and concrete examples for connection setup, action discovery, and running actions. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection, but there are no validation checkpoints or error recovery guidance. The workflow for checking existing connections vs creating new ones could be clearer with explicit decision points. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the '1Forge Overview' section with bullet points (Quotes, Currency Pairs, Convert) is cryptic and unhelpful. No references to external files for advanced topics, though the skill may not need them. | 2 / 3 |
Total | 9 / 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 | |
d19a82b
Table of Contents
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.