CtrlK
BlogDocsLog inGet started
Tessl Logo

smugmug

SmugMug integration. Manage Users. Use when the user wants to interact with SmugMug data.

56

Quality

65%

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/smugmug/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a strong, highly actionable skill body with excellent executable examples and a well-instrumented connection workflow. Its main weaknesses are inline bulk reference content that belongs in separate files and minor conciseness padding.

Suggestions

Move the 20-row "Popular actions" table and the proxy-options table into a references/ file (e.g. ACTIONS.md), keeping only a few key examples inline.

Label the workflow steps explicitly (Step 1, Step 2) so the dangling "skip to Step 2" reference resolves.

Add a brief validation/check step before destructive actions like delete-album, delete-image, and delete-node.

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable commands throughout, but the opening platform description and the 20-row inline "Popular actions" table add bulk that could be trimmed or externalized.

3 / 5

Actionability

It provides copy-paste ready bash commands for install, login, connection setup, action search, action execution, and proxy requests, with clear placeholders for dynamic values.

5 / 5

Workflow Clarity

The connection setup is a well-sequenced flow with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-after-action feedback loop, but the destructive delete-album/delete-image/delete-node operations have no validation or verification steps, which caps this dimension at 3.

3 / 5

Progressive Disclosure

Section headers give reasonable structure, but there are no bundle/reference files at all and the large action and proxy-option tables are inlined content that would be better split out.

3 / 5

Total

14

/

20

Passed

Description

66%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 correctly answers both what and when and is highly distinct thanks to the named platform, but its capability list is thin and the trigger phrasing is generic. Expanding the action coverage and trigger synonyms would lift specificity and trigger_term_quality.

Suggestions

Replace "Manage Users" with a fuller action list, e.g. "Manage SmugMug users, albums, folders, and images."

Broaden the trigger to natural phrases users actually say, e.g. "Use when the user wants to manage SmugMug photos, albums, galleries, or folders."

Drop redundant phrasing so the description reads as one tight sentence rather than fragmentary clauses.

DimensionReasoningScore

Specificity

The description names the domain ("SmugMug integration") and one concrete action target ("Manage Users"), but coverage is not comprehensive and omits the albums, folders, and images that dominate the actual skill.

3 / 5

Completeness

Both a "what" ("SmugMug integration. Manage Users.") and a "when" ("Use when the user wants to interact with SmugMug data.") are present, though the trigger could be more specific.

4 / 5

Trigger Term Quality

It includes a relevant keyword ("SmugMug") and a natural-ish phrase ("interact with SmugMug data"), but lacks common variations or synonyms like photos, albums, galleries, or image hosting.

3 / 5

Distinctiveness Conflict Risk

SmugMug is a specific named platform, giving the skill a clear niche with distinct triggers and minimal risk of firing for the wrong skill.

5 / 5

Total

15

/

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.