3scribe
3Scribe integration. Manage data, records, and automate workflows. Use when the user wants to interact with 3Scribe 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/3scribe/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 having a clear 'Use when' clause and naming the specific product (3Scribe), but it is severely lacking in specificity about what concrete actions the skill can perform. The capabilities listed are generic enough to describe almost any data management tool, making it hard for Claude to confidently select this skill based on user intent beyond explicit mentions of '3Scribe'.
Suggestions
Replace vague terms like 'manage data' and 'automate workflows' with specific concrete actions (e.g., 'create and update 3Scribe records, run transcription jobs, export reports').
Add more natural trigger terms users might say, such as specific 3Scribe features, record types, or common task names associated with the platform.
Expand the 'Use when' clause to include specific scenarios beyond just 'interact with 3Scribe data' (e.g., 'Use when the user mentions 3Scribe, transcription records, or wants to automate 3Scribe workflows').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without listing any concrete actions. There are no specific operations described (e.g., create records, query tables, trigger automations). | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with 3Scribe data), with an explicit 'Use when' clause. Though the what is vague, the structure is complete. | 3 / 3 |
Trigger Term Quality | It includes the product name '3Scribe' which is a useful trigger term, and mentions 'data', 'records', and 'workflows'. However, these are generic terms that users might use for many different tools, and it lacks specific variations or natural phrases users would say. | 2 / 3 |
Distinctiveness Conflict Risk | The product name '3Scribe' provides some distinctiveness, but 'manage data, records, and automate workflows' is extremely generic and could overlap with many database, CRM, or automation skills. The trigger clause narrows it to '3Scribe data' which helps somewhat. | 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 3Scribe via Membrane, with good coverage of the full workflow from installation to running actions. However, it wastes tokens on unnecessary introductory context about what 3Scribe is, includes a nearly empty overview section, and the popular actions table lacks descriptions. The content is largely a generic Membrane integration template with minimal 3Scribe-specific guidance.
Suggestions
Remove the introductory paragraph explaining what 3Scribe is and the empty '3Scribe Overview' section — Claude doesn't need this context and it wastes tokens.
Fill in the descriptions for the popular actions table, or remove it if descriptions aren't available — empty cells reduce actionability.
Add 3Scribe-specific examples (e.g., a concrete example of creating a transcription job with actual input parameters) to differentiate this from a generic Membrane skill.
Consider extracting the generic Membrane CLI workflow (install, auth, connect, action lifecycle) into a shared reference file and keeping only 3Scribe-specific content inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what 3Scribe is (transcription software, used by content creators, etc.) is unnecessary context Claude doesn't need. The '3Scribe Overview' section with just 'File > Transcription > Workspace' adds no value. The best practices section has some filler. However, the CLI commands themselves are reasonably lean. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, and running actions with parameters. The commands include specific flags and JSON input examples. | 3 / 3 |
Workflow Clarity | The steps are presented in a logical sequence (install → authenticate → connect → search → create/run), and the action creation flow includes polling with state checking. However, there are no explicit validation checkpoints or error recovery feedback loops for the overall workflow. The 'Popular actions' table has empty description fields, reducing clarity. | 2 / 3 |
Progressive Disclosure | The content is structured with clear headers and sections, and references official docs. However, it's somewhat monolithic — the Membrane CLI usage patterns (authentication, connection, action lifecycle) are generic across many integrations and could be referenced rather than inlined. The '3Scribe Overview' section is skeletal and unhelpful. | 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.