accountscore
AccountScore integration. Manage data, records, and automate workflows. Use when the user wants to interact with AccountScore data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill accountscore72
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
67%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 includes an explicit 'Use when...' clause and identifies the specific integration (AccountScore), which aids in skill selection. However, the capabilities listed are vague ('manage data', 'automate workflows') rather than concrete actions, and the trigger terms lack natural variations users might employ when requesting AccountScore-related tasks.
Suggestions
Replace vague verbs with specific actions (e.g., 'Create and update customer records, pull credit scores, generate financial reports, sync account data').
Add natural trigger term variations users might say (e.g., 'credit scoring', 'financial data', 'account analysis', specific AccountScore feature names).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AccountScore) and mentions general actions ('Manage data, records, and automate workflows'), but these are not concrete specific actions - 'manage' and 'automate workflows' are vague. No specific operations like 'create records', 'run reports', or 'sync contacts' are listed. | 2 / 3 |
Completeness | Has both 'what' (manage data, records, automate workflows) and 'when' (explicit 'Use when the user wants to interact with AccountScore data'). The 'Use when...' clause is present and provides clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes 'AccountScore' as a key trigger term and generic terms like 'data' and 'records', but lacks natural variations users might say (e.g., 'account scoring', 'credit data', 'financial records', specific feature names). The term 'workflows' is somewhat generic. | 2 / 3 |
Distinctiveness Conflict Risk | 'AccountScore' is a specific product name which helps distinctiveness, but 'manage data, records, and automate workflows' is generic enough to potentially conflict with other CRM, database, or automation skills. The trigger 'interact with AccountScore data' is specific but the capabilities overlap with many integration skills. | 2 / 3 |
Total | 9 / 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 AccountScore integration via Membrane, with good examples for common operations. However, it includes unnecessary introductory content about what AccountScore is, lacks validation checkpoints in workflows, and the overview section adds no practical value. The best practices section is useful but the overall structure could be tightened.
Suggestions
Remove the introductory paragraph explaining what AccountScore is - Claude doesn't need this context to execute the integration
Remove or replace the empty 'AccountScore Overview' bullet section with actual useful quick-reference content
Add validation steps after key operations (e.g., 'Verify connection succeeded by running membrane connection list')
Add error handling guidance for common failure scenarios (authentication failures, invalid action IDs)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., explaining what AccountScore is as a SaaS application, which Claude doesn't need). The overview section with bullet points adds little value. However, the CLI commands and examples are reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with clear syntax examples. Commands are copy-paste ready with proper flags and JSON parameter passing demonstrated. The proxy request section includes a helpful options table. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack validation checkpoints. No explicit verification steps after running actions or connections. The workflow for headless environments is mentioned but could be clearer with numbered steps and success/failure handling. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The 'AccountScore Overview' section with nested bullets adds no value and could be removed. No references to external files for advanced topics or detailed API documentation. | 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.