addevent
Addevent integration. Manage data, records, and automate workflows. Use when the user wants to interact with Addevent data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill addevent61
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
40%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 relies heavily on users already knowing what Addevent is, providing minimal context about its purpose (event/calendar management). The generic phrases 'manage data, records, and automate workflows' could describe almost any integration, and the description lacks specific actions or natural trigger terms that would help Claude select this skill appropriately.
Suggestions
Replace generic phrases with specific Addevent capabilities (e.g., 'Create and manage calendar events, send event invitations, track RSVPs, embed add-to-calendar buttons').
Add natural trigger terms users would say: 'calendar events', 'event invitations', 'RSVP tracking', 'add-to-calendar links', 'event scheduling'.
Expand the 'Use when...' clause with concrete scenarios: 'Use when the user wants to create shareable calendar events, manage event invitations, or add calendar functionality to their application.'
| 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 Addevent is or what specific operations can be performed (e.g., create events, send invitations, track RSVPs). | 1 / 3 |
Completeness | Has a 'Use when...' clause but it's circular ('interact with Addevent data'). The 'what' is too vague ('manage data, records') and the 'when' doesn't provide meaningful trigger guidance beyond knowing the product name. | 2 / 3 |
Trigger Term Quality | Includes 'Addevent' as a trigger term which users familiar with the service would use, but lacks natural variations like 'calendar events', 'event invitations', 'RSVP', 'event scheduling', or 'calendar integration' that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is generic phrasing that could apply to dozens of integrations. Only 'Addevent' provides distinctiveness, but users unfamiliar with the product wouldn't know when to use this skill. | 2 / 3 |
Total | 7 / 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 Addevent integration via Membrane, with good coverage of common operations. However, it includes unnecessary platform description, lacks validation/error handling in workflows, and the action table with empty descriptions adds bulk without value. The structure is adequate but could benefit from better progressive disclosure.
Suggestions
Remove the introductory paragraph explaining what Addevent is - Claude already knows this context
Add validation steps after connection creation (e.g., 'Verify connection: membrane connection list --json | grep CONNECTION_ID')
Either add descriptions to the action table entries or remove the table and rely on 'membrane action list --intent' for discovery
Add error handling guidance for common failure scenarios (auth failures, rate limits, invalid inputs)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary explanation (e.g., 'Addevent is a platform that simplifies event scheduling...' is context Claude doesn't need). The action table with 'No description' entries adds bulk without value. | 2 / 3 |
Actionability | Provides concrete, executable CLI commands throughout with clear syntax examples. Commands are copy-paste ready with proper flags and JSON output options documented. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack validation checkpoints. No error handling guidance for failed connections or actions. The workflow jumps between checking existing connections and creating new ones without clear decision logic. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but the action table is verbose and could be linked to external reference. No references to additional documentation files for advanced use cases or detailed API reference. | 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 | |
- 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.