CtrlK
BlogDocsLog inGet started
Tessl Logo

templated

Templated integration. Manage data, records, and automate workflows. Use when the user wants to interact with Templated data.

54

Quality

61%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/templated/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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.

The body is action-rich with executable CLI commands and a reasonable connection-readiness flow, but it includes some unnecessary explanation and the multi-step workflow lacks explicit validation checkpoints and clean step labeling.

Suggestions

Tighten the intro to one purpose line and remove the audience sentence; lean on Claude's existing knowledge of what document automation is.

Replace the dangling "skip to Step 2" reference with clearly numbered steps (1. Connect, 2. Discover actions, 3. Run) and add an explicit verify step after action run / proxy calls.

Trim redundant restatements such as repeating the action list discovery command in both "Searching for actions" and "Popular actions".

DimensionReasoningScore

Conciseness

Mostly command-driven and efficient, but the marketing-style intro ("used by professionals in sales, marketing, and HR") and a few redundant restatements add unnecessary tokens.

3 / 5

Actionability

Provides concrete, copy-paste-ready commands for install, login, connection, action search/run, and proxying, with only minor gaps (e.g. placeholder substitution).

4 / 5

Workflow Clarity

A rough sequence exists (install, auth, connect, poll for READY, search, run) with state polling, but it references an unlabeled "Step 2" and lacks explicit validation checkpoints for run/proxy operations.

3 / 5

Progressive Disclosure

Single well-organized SKILL.md with clear section headers and no nested references; minor gap is that all API/proxy detail lives inline with no separate reference file.

4 / 5

Total

14

/

20

Passed

Description

62%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.

The description identifies a concrete product and includes an explicit use-when trigger, but its capability list is generic (manage data/records/automate workflows) and lacks natural keyword variations.

Suggestions

Replace generic verbs ("Manage data, records, automate workflows") with concrete Templated actions like "create documents from templates, render images/PDFs from templates, manage template fields".

Expand the trigger clause with natural user phrasings and file/term synonyms, e.g. "Use when the user wants to generate documents, render templates, or mentions Templated, template-driven documents, or document automation".

DimensionReasoningScore

Specificity

Names the domain ("Templated integration") and a few actions ("Manage data, records, and automate workflows"), but the actions are generic and coverage is not comprehensive.

3 / 5

Completeness

Provides both a "what" (manage data, records, automate workflows) and an explicit "when" clause; the "when" is present but could be more specific.

4 / 5

Trigger Term Quality

Contains an explicit trigger ("Use when the user wants to interact with Templated data") but only one natural phrase, missing common variations or synonyms.

3 / 5

Distinctiveness Conflict Risk

Names a specific product ("Templated") with product-scoped triggers, making it mostly distinct with only minor overlap risk against generic data skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.