CtrlK
BlogDocsLog inGet started
Tessl Logo

generic-assistant

Fallback authoring playbook for building general-purpose personal assistant agents that do not fit a more specific archetype. Use this only after checking the other archetype skills (coding, spreadsheet, research, customer-support, content-writer, ops-automation). Examples include summarizing emails, drafting short answers, capturing notes, or generic personal-helper agents.

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, actionable authoring playbook with a complete template and a concrete worked example. It is reference-style rather than workflow-driven, so sequence and validation are implied rather than explicitly numbered.

Suggestions

Add a short numbered authoring workflow (e.g. 1. confirm generic scope, 2. fill identity template, 3. fill system prompt, 4. check anti-patterns, 5. verify completion criteria) to make the sequence and validation checkpoints explicit.

Trim the 'Required behavioral rules to enforce' section or fold it into the template to remove the duplication with the system prompt template's Decisiveness/Scope/Completion criteria.

DimensionReasoningScore

Conciseness

Lean playbook that assumes Claude's competence and avoids explaining basic concepts; the only padding is the 'Required behavioral rules' section restating Decisiveness/Scope/Completion criteria already detailed in the template, a minor trim opportunity.

4 / 5

Actionability

Provides a complete copy-paste-ready system prompt template, concrete name/description patterns, explicit anti-patterns, and a fully worked example covering the representative case; guidance is highly actionable for an instruction-only skill.

5 / 5

Workflow Clarity

The worked example supplies the authoring sequence (request -> name, description, model, tools, prompt) and completion criteria plus anti-pattern rejection act as checkpoints; minor gap is that the sequence is implied rather than an explicit numbered procedure.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no nested references and no bundle files to navigate; the inline system-prompt template block is appropriately core content, leaving only minor organization gaps versus a 5.

4 / 5

Total

17

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-gated fallback description that clearly answers what and when with concrete trigger phrases. The main weakness is second-person phrasing, which costs it specificity per the rubric.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete example actions ('summarizing emails, drafting short answers, capturing notes'), which would anchor at 4, but the second-person 'Use this only after checking...' triggers the rubric's -1 specificity penalty.

3 / 5

Completeness

Explicitly states both what ('Fallback authoring playbook for building general-purpose personal assistant agents') and when ('Use this only after checking the other archetype skills...') with concrete trigger examples, matching the top anchor.

5 / 5

Trigger Term Quality

Good coverage of natural phrases users actually say ('summarize my emails', 'personal assistant', 'personal-helper agents', 'capturing notes'); a few common synonyms are absent but not enough for a 5.

4 / 5

Distinctiveness Conflict Risk

Enumerates all sibling archetypes and gates itself as a fallback, making it mostly distinct with only minor overlap risk; inherent catch-all breadth keeps it just below 5.

4 / 5

Total

16

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mastra-ai/mastra
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.