3scribe
3Scribe integration. Manage data, records, and automate workflows. Use when the user wants to interact with 3Scribe data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill 3scribe72
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.
This description provides basic structure with a 'Use when' clause but lacks specificity in its capabilities. The actions described are vague ('manage', 'automate') rather than concrete operations. The 3Scribe brand name helps with distinctiveness, but the description would benefit from more specific actions and natural trigger terms users would actually say.
Suggestions
Replace vague verbs with specific actions: instead of 'Manage data, records', list concrete operations like 'Create, update, and query records', 'Generate reports', or 'Configure automation rules'
Add natural trigger terms users would say, such as specific 3Scribe features, record types, or common use cases (e.g., 'transcripts', 'meeting records', 'workflow triggers' - whatever is relevant to 3Scribe)
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (3Scribe) 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', 'query tables', or 'trigger automations' are listed. | 2 / 3 |
Completeness | Has both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with 3Scribe data). The explicit 'Use when...' clause is present, though the trigger condition is somewhat circular. | 3 / 3 |
Trigger Term Quality | Includes '3Scribe' as a trigger term and generic terms like 'data' and 'records', but lacks natural variations users might say. Missing terms like 'transcription', 'audio', 'meeting notes' if applicable, or specific feature names that users would mention. | 2 / 3 |
Distinctiveness Conflict Risk | The '3Scribe' brand name provides some distinctiveness, but 'manage data, records, and automate workflows' is generic enough to potentially conflict with other database or workflow automation skills. The trigger 'interact with 3Scribe data' helps but is narrow. | 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 3Scribe integration via Membrane, with good coverage of common operations and proxy requests. However, it wastes tokens on introductory context Claude doesn't need, lacks validation/error handling guidance in workflows, and has an unexplained overview section that adds confusion rather than clarity.
Suggestions
Remove the opening paragraph explaining what 3Scribe is - Claude already knows this and it wastes tokens
Add validation steps after key operations (e.g., 'Verify connection succeeded by running membrane connection list --json and confirming the connection appears')
Either expand the '3Scribe Overview' section to explain what File/Transcription/Workspace mean in context, or remove it entirely if it's not actionable
Add error handling guidance for common failure scenarios (authentication timeout, invalid action ID, connection not found)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what 3Scribe is (transcription software, used by content creators, etc.) is unnecessary context Claude already knows. The rest is reasonably efficient but could be tighter. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, including JSON parameter passing, proxy requests with flag documentation, and concrete examples for each operation. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection, but lacks validation checkpoints. No guidance on verifying successful connection, handling failed authentication, or confirming action execution succeeded. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the 'Overview' section with File/Transcription/Workspace hierarchy is cryptic and unexplained. Links to external docs but no internal file references for advanced topics. | 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.