CtrlK
BlogDocsLog inGet started
Tessl Logo

adobe-automation

Automate Adobe tasks via Rube MCP (Composio). Always search tools first for current schemas.

70

7.07x
Quality

55%

Does it follow best practices?

Impact

99%

7.07x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./composio-skills/adobe-automation/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 well-structured with actionable tool-call templates and a clear workflow, but it repeats the 'search first' guidance and omits an explicit validation feedback loop around the batch execute step. Tightening repetition and adding a verify-after-execute checkpoint would raise the score.

Suggestions

State the 'always search tools first' rule once (e.g., in Prerequisites) and reference it elsewhere instead of repeating the full guidance four times.

Add an explicit validate/verify step after RUBE_MULTI_EXECUTE_TOOL (e.g., inspect responses for errors/pagination, retry or surface failures before proceeding) to satisfy the batch-operation feedback-loop expectation.

Replace placeholder arguments in the execute example with a concrete worked example (real tool slug + realistic arguments) to move from template to copy-paste-ready.

DimensionReasoningScore

Conciseness

The body is mostly efficient but 'always search tools first' is restated in Prerequisites, Tool Discovery, Core Workflow Step 1, and Known Pitfalls, which is noticeable padding that could be tightened.

3 / 5

Actionability

Concrete tool-call templates with named parameters are provided for each step, but arguments remain placeholders ('TOOL_SLUG_FROM_SEARCH', 'your specific Adobe task'), leaving minor gaps from copy-paste-ready.

4 / 5

Workflow Clarity

Discover -> Check connection -> Execute is clearly sequenced with an ACTIVE-status checkpoint, but the batch RUBE_MULTI_EXECUTE_TOOL step lacks an explicit post-execute validation/verification feedback loop, which caps workflow clarity at 3 per the batch-operations guideline.

3 / 5

Progressive Disclosure

A single well-organized file with clear section headers (Prerequisites, Setup, Tool Discovery, Workflow, Pitfalls, Quick Reference) and no external bundle files; minor gap only because no one-level-deep references segment advanced detail.

4 / 5

Total

14

/

20

Passed

Description

48%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 clearly identifies the domain and toolchain but stays generic about capabilities and omits any 'Use when...' trigger guidance. Adding concrete Adobe operations and explicit trigger phrases would lift specificity and completeness.

Suggestions

List 2-3 concrete operations (e.g., 'create and edit PDFs, export assets from Photoshop, automate Illustrator actions') instead of the generic 'Adobe tasks'.

Add an explicit 'Use when...' clause naming natural user triggers (e.g., 'Use when automating Adobe Creative Cloud workflows, batch-exporting assets, or scripting Photoshop/Illustrator').

Include common synonyms and file extensions (Photoshop, Illustrator, .psd, .ai) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the Adobe domain but the action ('Automate Adobe tasks') is generic with no concrete operations enumerated, matching the 'names domain but actions minimal/generic' anchor rather than the 1 (purely abstract) or 3 (1-2 concrete actions).

2 / 5

Completeness

The 'what' ('Automate Adobe tasks via Rube MCP') is clear but no 'Use when...' / trigger guidance is present, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

'Adobe' is a relevant keyword but common synonyms and product/file cues users actually say (Photoshop, Illustrator, PDF, .ai, .psd) are absent, matching 'some relevant keywords but missing common variations.'

3 / 5

Distinctiveness Conflict Risk

The Adobe + Rube MCP (Composio) niche is mostly distinct with only minor overlap risk against other automation skills, fitting 'mostly distinct; minor overlap risk.'

4 / 5

Total

12

/

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
ComposioHQ/awesome-claude-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.