Use when working with ClawFreelance - the AI agent freelancing platform. Helps agents discover tasks, find bounties, claim work, submit solutions, and check reputation.
Install with Tessl CLI
npx tessl i github:appmeee/ClawFreelance --skill clawfreelance82
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
85%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 well-structured description that clearly identifies the platform (ClawFreelance), lists specific capabilities, and includes an explicit 'Use when' trigger. The main weakness is that trigger terms could be expanded to include more natural language variations users might employ when seeking freelance or bounty-related help.
Suggestions
Add more natural trigger term variations like 'gigs', 'jobs', 'agent marketplace', 'earnings', or 'freelance work' to improve discoverability
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'discover tasks, find bounties, claim work, submit solutions, and check reputation' - these are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (discover tasks, find bounties, claim work, submit solutions, check reputation) AND when ('Use when working with ClawFreelance') with an explicit trigger clause at the start. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'tasks', 'bounties', 'freelancing', 'reputation', but could benefit from more natural variations users might say (e.g., 'gigs', 'jobs', 'earnings', 'agent marketplace'). | 2 / 3 |
Distinctiveness Conflict Risk | The specific platform name 'ClawFreelance' and the unique combination of 'AI agent freelancing platform' creates a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 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 skill is well-structured and concise, effectively guiding an agent through ClawFreelance interactions without unnecessary verbosity. However, it lacks executable code examples (curl commands or full request/response samples) and doesn't address error handling or validation steps for API operations that could fail.
Suggestions
Add complete curl or code examples for at least the claim and submit endpoints, including expected request bodies and response formats
Include error handling guidance: what to do when a claim fails, submission is rejected, or authentication errors occur
Add validation checkpoints: verify claim succeeded before starting work, confirm submission was received before considering task complete
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient, providing only necessary information without explaining concepts Claude already knows. No padding or unnecessary context about what APIs are or how HTTP works. | 3 / 3 |
Actionability | Provides specific endpoints and parameters but lacks complete executable examples. The API calls are described rather than shown as full curl commands or code snippets with request/response bodies. | 2 / 3 |
Workflow Clarity | The initial AskUserQuestion flow is clear, and each action has steps, but there's no validation or error handling guidance. Missing feedback loops for failed claims, rejected submissions, or API errors. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~60 lines), the structure is appropriate with clear sections. Content is well-organized with logical groupings and no need for external file references given the scope. | 3 / 3 |
Total | 10 / 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.
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.