agenty
Agenty integration. Manage data, records, and automate workflows. Use when the user wants to interact with Agenty data.
54
61%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/agenty/SKILL.mdQuality
Discovery
57%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description benefits from having an explicit 'Use when...' clause and naming the specific product (Agenty), but it is severely lacking in specificity about what concrete actions the skill can perform. The generic terms 'data', 'records', and 'workflows' provide almost no useful information for distinguishing this skill from other data management or automation skills.
Suggestions
Replace vague terms like 'manage data, records, and automate workflows' with specific Agenty capabilities (e.g., 'create and query Agenty agents, manage scraping jobs, retrieve collection records, configure automation rules').
Expand trigger terms in the 'Use when...' clause to include natural phrases users might say, such as 'web scraping', 'Agenty agents', 'Agenty collections', or specific Agenty feature names.
Add file types, API concepts, or domain-specific terms that would help Claude distinguish this skill from generic data management skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying concrete actions. What kind of data? What records? What workflows? These are abstract terms that don't describe specific capabilities. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with Agenty data). The 'Use when...' clause is explicitly present, though both parts are quite vague in substance. | 3 / 3 |
Trigger Term Quality | It includes the product name 'Agenty' which is a useful trigger term, and mentions 'data', 'records', and 'workflows'. However, it lacks specific natural language terms users might say (e.g., specific Agenty features, scraping, agents, collections) and the generic terms could match many other skills. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Agenty' as a specific product name helps distinguish it, but 'manage data, records, and automate workflows' is extremely generic and could overlap with many other integration or data management skills. | 2 / 3 |
Total | 8 / 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.
The skill provides solid, actionable CLI commands for integrating with Agenty via Membrane, with good coverage of the connection lifecycle and action discovery. However, it suffers from some unnecessary verbosity (introductory explanation, empty table descriptions, bare overview list), and the workflow could benefit from clearer top-level sequencing and explicit validation checkpoints after action execution.
Suggestions
Remove the introductory paragraph explaining what Agenty is and the bare 'Agenty Overview' bullet list — Claude already knows this and it wastes tokens.
Either populate the Description column in the popular actions table or remove it entirely to avoid empty cells that waste space.
Add a clear top-level numbered workflow (1. Install → 2. Authenticate → 3. Connect → 4. Discover actions → 5. Run actions) to improve workflow clarity and make the overall process scannable.
Consider splitting the proxy requests section and connection state machine details into separate reference files to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes some unnecessary explanation (e.g., 'Agenty is a web scraping and automation platform. It's used by businesses and developers to extract data from websites, automate tasks, and integrate with other applications.' — Claude knows this). The popular actions table has empty description columns, wasting tokens. The Agenty Overview section is a bare bullet list that adds little value. However, the CLI commands and workflow steps are reasonably tight. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear parameter placeholders and flag descriptions. | 3 / 3 |
Workflow Clarity | The connection setup workflow has a reasonable sequence with state-based branching (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), but there's no explicit validation checkpoint after running actions. The overall flow from install → auth → connect → discover → run is present but could be more explicitly sequenced with numbered top-level steps and clearer error recovery loops. | 2 / 3 |
Progressive Disclosure | The content is structured with headers and sections, but it's somewhat monolithic — the proxy request details, popular actions table, and connection state machine details could be split into separate reference files. There are no references to bundle files since none exist, and the single-file approach makes it harder to navigate for a skill of this length. | 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 | |
- Repository
- membranedev/application-skills
- Commit
f484c82
- 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.