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.

71

Quality

86%

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

86%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 well-structured, highly actionable playbook: a copy-paste system prompt template, explicit behavioral rules with completion criteria, and a full worked example, all in a clean self-contained layout. The main gaps are mild redundancy with the frontmatter description and the absence of an explicitly numbered authoring sequence.

Suggestions

Trim the 'When to use' section to a pointer to the archetype list instead of restating all six sibling skills already named in the description.

Add a short numbered authoring sequence (check archetypes → pick name/description → fill the prompt template → attach minimal tools → verify completion criteria) so the workflow order is explicit rather than implied by section order.

DimensionReasoningScore

Conciseness

The body is lean — templates, rules, and anti-patterns carry the content with no explanation of concepts Claude already knows. Minor redundancy remains: the "When to use" section restates the archetype list from the description, and "Anti-patterns" repeats the scope and completion rules, so it fits anchor 4 rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

A full copy-paste system prompt template with explicit placeholder semantics, plus a complete worked example (name, description, model, attached tools, prompt excerpt) covering the common case. This matches anchor 5: executable, copy-paste ready guidance with a specific example.

5 / 5

Workflow Clarity

Sections follow a coherent order (when-to-use, identity, prompt template, rules, capabilities, anti-patterns, worked example) and "Required behavioral rules to enforce in the produced prompt" plus the completion criteria act as explicit validation checkpoints for the artifact. However, the authoring sequence itself is never enumerated as steps, so it sits at anchor 4 rather than 5; it is above anchor 3 because checkpoints are explicit, not implicit.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed — this single-purpose authoring playbook is self-contained, with the 35-line template appropriately inline as core content. Clean, well-organized section headers make navigation easy, matching anchor 5 for a well-organized self-contained skill.

5 / 5

Total

18

/

20

Passed

Description

87%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 description that clearly states what the skill does, when to use it relative to six named sibling skills, and concrete example use cases in third person. Trigger coverage is good but a few natural phrasings users would say are absent.

DimensionReasoningScore

Specificity

"Fallback authoring playbook for building general-purpose personal assistant agents" names the domain and concrete action in third person, with example targets like "summarizing emails, drafting short answers, capturing notes". It lists several specific actions but the skill's own capability coverage rests on a single verb (build), so it fits anchor 4 rather than the comprehensive anchor 5.

4 / 5

Completeness

It explicitly answers what ("authoring playbook for building general-purpose personal assistant agents") and when ("Use this only after checking the other archetype skills (coding, spreadsheet, research, customer-support, content-writer, ops-automation)") with concrete example triggers. Both are explicit and concrete, matching anchor 5.

5 / 5

Trigger Term Quality

Natural phrases like "summarizing emails", "drafting short answers", "capturing notes", and "generic personal-helper agents" mirror what users would actually say. Coverage is good but misses common variations such as "be my assistant" or "take notes", matching anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

It enumerates the six sibling archetype skills and positions itself strictly as a fallback after checking them, plus concrete fallback examples. This active disambiguation gives a clear niche with minimal conflict risk, matching anchor 5.

5 / 5

Total

18

/

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.

Validation — 16 / 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.