aidaform
Aidaform integration. Manage data, records, and automate workflows. Use when the user wants to interact with Aidaform data.
55
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/aidaform/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 correctly identifies the integration target (Aidaform) and includes an explicit 'Use when' clause, which is good. However, it is severely lacking in specificity—the actions described are generic enough to apply to almost any data management tool. It also misses key trigger terms like 'forms', 'submissions', or 'survey' that users would naturally use when needing this skill.
Suggestions
Add specific concrete actions such as 'retrieve form submissions, create forms, export survey responses, manage form fields' to replace the vague 'manage data, records, and automate workflows'.
Include natural trigger terms users would say, such as 'forms', 'submissions', 'survey', 'form responses', 'Aidaform forms' in both the capability description and the 'Use when' clause.
Expand the 'Use when' clause to cover specific scenarios, e.g., 'Use when the user mentions Aidaform, needs to retrieve form submissions, create surveys, or export form response data.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without listing any concrete actions specific to Aidaform. There are no specific capabilities mentioned such as creating forms, retrieving submissions, or exporting responses. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with Aidaform data), with an explicit 'Use when...' clause. However, both parts are quite thin in detail. | 3 / 3 |
Trigger Term Quality | It includes 'Aidaform' as a key trigger term and mentions 'data' and 'workflows', but misses natural terms users might say like 'forms', 'submissions', 'responses', 'form builder', or 'survey'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is very generic and could overlap with many integration skills. The mention of 'Aidaform' specifically helps distinguish it, but the rest of the description is not distinctive enough. | 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.
This is a functional integration skill with good actionability — the CLI commands are concrete and executable. However, it suffers from some unnecessary introductory content, a vacuous overview section, and lacks validation/error-handling guidance in its workflows. The proxy request documentation is a strong addition that adds real value.
Suggestions
Remove the introductory paragraph explaining what Aidaform is — Claude already knows this, and the skill description covers it.
Add error handling guidance: what to do when connection fails, when action list returns no results, or when action run produces errors (feedback loops).
Either flesh out the 'Aidaform Overview' section with actual action IDs and their purposes, or remove it — the current 'Forms / Contacts' bullet list with 'Use action names and parameters as needed' provides no actionable information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'Aidaform is a form builder that allows users to create surveys, quizzes, and contact forms. It's used by marketers, researchers, and small businesses...') that Claude already knows. The overview section with 'When to use which actions: Use action names and parameters as needed' is vacuous. However, the CLI commands themselves are reasonably lean. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: login, search connectors, connect, list connections, search actions, run actions with parameters, and proxy requests. The flag reference table for proxy requests is specific and useful. | 3 / 3 |
Workflow Clarity | The setup and connection workflow is sequenced clearly (login → search connector → connect → list actions → run). However, there are no validation checkpoints or error recovery steps — no guidance on what to do if connection fails, if action list returns empty, or if action run produces errors. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's somewhat monolithic for its length. The overview section ('Forms → Form Submissions, Contacts') is too sparse to be useful, and there are no references to external files. For a skill with no bundle files, the organization is adequate but the overview section adds little value. | 2 / 3 |
Total | 9 / 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
- 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.