CtrlK
BlogDocsLog inGet started
Tessl Logo

comfyui-gateway

REST API gateway for ComfyUI servers. Workflow management, job queuing, webhooks, caching, auth, rate limiting, and image delivery (URL + base64).

60

Quality

71%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/comfyui-gateway/SKILL.md

The canonical home for this skill is comfyui-gateway in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 highly actionable with executable quick-start and CLI commands plus a well-signaled two-file reference layer. It loses points to generic boilerplate sections and to the absence of explicit validation checkpoints in the job lifecycle and quick-start workflows.

Suggestions

Remove or replace the generic Best Practices / Common Pitfalls / Related Skills filler with ComfyUI-gateway-specific guidance, or drop those sections entirely to tighten conciseness.

Insert validation checkpoints into the Job Lifecycle and Quick Start (e.g. run `npx tsx src/cli/index.ts health` to confirm ComfyUI reachability before starting, and verify a workflow registered before submitting a job) to lift workflow clarity past the cap.

De-duplicate the Overview and How It Works sections, which currently restate the same capability list, to reclaim token budget.

DimensionReasoningScore

Conciseness

Core reference material (endpoints, env table, security model) is efficient, but the Overview/How It Works sections restate the description and the Best Practices/Common Pitfalls/Related Skills blocks are generic filler that earns no tokens.

3 / 5

Actionability

Quick Start, CLI reference, env var table, and the workflow-template JSON example are concrete and copy-paste ready, covering the common cases end to end.

5 / 5

Workflow Clarity

The Job Lifecycle is a clear sequenced 9-step flow, but it (and the Quick Start) lack explicit validation checkpoints for batch/destructive GPU and DB operations, which per the rubric caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Two real one-level-deep references (references/troubleshooting.md, references/integration.md) are clearly signaled, and the inline overview is well sectioned; a fair amount of detail is inlined rather than split out, keeping it just short of a 5.

4 / 5

Total

15

/

20

Passed

Description

75%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 is specific and clearly distinct, naming many concrete capabilities with strong ComfyUI-specific triggers. Its main weakness is the absence of any explicit use-when guidance, leaving Claude without trigger phrases in the frontmatter.

Suggestions

Append a "Use when ..." clause with concrete trigger phrases (e.g. "Use when the user wants a REST API in front of ComfyUI, job queuing, or webhooks for image generation") to lift completeness.

Add a natural synonym such as "stable diffusion" alongside "ComfyUI" so the description surfaces for those queries.

Keep the existing capability list but front-load the primary verb (e.g. "Wraps ComfyUI in a REST API gateway that ...") to make the action even more concrete.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — "Workflow management, job queuing, webhooks, caching, auth, rate limiting, and image delivery (URL + base64)" — giving comprehensive coverage of what the gateway does.

5 / 5

Completeness

Clearly answers "what" but provides no explicit "when to use" clause or trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms "ComfyUI" and "REST API gateway" that users would say, but misses common synonyms/extensions such as "stable diffusion" or "image generation"; good but not exhaustive coverage.

4 / 5

Distinctiveness Conflict Risk

"REST API gateway for ComfyUI servers" carves out a clear niche tied to ComfyUI, making false-trigger conflict with other skills minimal.

5 / 5

Total

17

/

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
administrakt0r/AI-Agents-Safe-Coding-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.