agenty
Agenty integration. Manage data, records, and automate workflows. Use when the user wants to interact with Agenty data.
68
61%
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/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 naming the specific product (Agenty) and including an explicit 'Use when' clause, but it is severely lacking in specificity about what concrete actions the skill performs. The generic terms 'data', 'records', and 'workflows' provide almost no useful information for distinguishing this skill from other data management or integration 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').
Add more natural trigger terms users might say, such as specific Agenty features, entity types, or common use cases (e.g., 'web scraping agents', 'Agenty collections', 'scraping results').
Expand the 'Use when' clause with more specific trigger scenarios (e.g., 'Use when the user mentions Agenty, web scraping agents, or wants to manage scraping jobs and their results').
| 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 thin on detail. | 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, or other domain-specific terms). | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is extremely generic and could overlap with many other integration or data management skills. The mention of 'Agenty' specifically helps distinguish it, but the rest of the description is broad enough to cause conflicts. | 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, covering the full lifecycle from installation to running actions. However, it includes some dead-weight content (empty description columns in the actions table, the vague Agenty Overview section) and lacks validation checkpoints for error-prone operations like connection setup and action execution. The workflow is implicitly sequenced but would benefit from explicit verification steps.
Suggestions
Remove or populate the empty Description column in the popular actions table — empty cells waste tokens without providing value.
Remove or condense the 'Agenty Overview' bullet list, which provides no actionable information.
Add explicit validation/verification steps after connection creation (e.g., verify connection status) and after action runs (e.g., check output for errors).
Add a brief error-handling section or feedback loop for failed action runs, not just for action creation polling.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary explanation (e.g., 'Agenty is a web scraping and automation platform' and the overview bullet list that adds no actionable value). The popular actions table has empty description columns, wasting tokens. The Agenty Overview section is particularly unhelpful. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, running actions with parameters. Each command includes specific flags and options. | 3 / 3 |
Workflow Clarity | The workflow is reasonably sequenced (install → authenticate → connect → search/create actions → run), but there are no explicit validation checkpoints or error recovery loops beyond the action creation polling. For instance, there's no guidance on verifying a connection succeeded or handling failed action runs. | 2 / 3 |
Progressive Disclosure | The content is structured with clear sections and headers, but it's somewhat monolithic — the popular actions table and best practices could be separate references. The link to official docs is good, but there are no references to supplementary files for advanced usage patterns. | 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
56d7336
- 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.