CtrlK
BlogDocsLog inGet started
Tessl Logo

graphql

You're a developer who has built GraphQL APIs at scale. You've seen the N+1 query problem bring down production servers. You've watched clients craft deeply nested queries that took minutes to resolve. You know that GraphQL's power is also its danger.

38

Quality

36%

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/graphql/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

47%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 a well-organized but shallow GraphQL reference catalog: it lists capabilities, patterns, anti-patterns, and a useful Sharp Edges table, yet provides no executable code, no workflow sequence, and no validation guidance for the risky operations it flags.

Suggestions

Add concrete, executable examples for the key patterns (e.g. a DataLoader batching snippet, a depth-limit/cost-analysis Apollo Server config) instead of one-line descriptions and hashtag labels.

Provide a sequenced workflow with validation checkpoints for risky actions — e.g. schema review → enable depth/cost limits → verify introspection disabled in production.

Complete the truncated "You've l" sentence and replace the vague "When to Use" filler with specific, concrete applicability conditions.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's GraphQL knowledge, with a compact Sharp Edges table and one-line Patterns; minor trimming needed from the persona block repeated from the description and the vague "When to Use" filler line.

4 / 5

Actionability

Guidance is high-level hints ("Batch and cache database queries", "# USE DATALOADER") with no executable code, commands, or specific steps — it describes patterns rather than instructing how to implement them.

2 / 5

Workflow Clarity

Sections are organized but there is no multi-step sequence or validation checkpoints for the critical-risk operations the Sharp Edges table itself enumerates (N+1, query depth DoS), leaving the workflow implicit.

2 / 5

Progressive Disclosure

Content is well-organized into clear sections (Capabilities, Patterns, Anti-Patterns, Sharp Edges, Related Skills) and is compact enough to be self-contained with no bundle files; minor blemishes from the truncated "You've l" line and filler When-to-Use.

4 / 5

Total

12

/

20

Passed

Description

26%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 an evocative second-person persona narrative that establishes domain credibility but fails to communicate what the skill does or when to use it. It lacks concrete actions, a Use-when trigger clause, and uses penalized second-person voice.

Suggestions

Rewrite in third person as a capability statement listing concrete actions, e.g. "Designs GraphQL schemas, prevents N+1 queries with DataLoader, and limits query depth/complexity."

Add an explicit trigger clause: "Use when building or reviewing GraphQL APIs (Apollo Server/Client, federation, subscriptions, codegen)."

Drop the war-story persona framing; replace it with specific, action-oriented capabilities and natural trigger terms users would actually say.

DimensionReasoningScore

Specificity

The description names the GraphQL domain but lists no concrete actions the skill performs ("You're a developer who has built GraphQL APIs at scale"), and the entirely second-person voice triggers the −1 specificity penalty, dropping a base score of 2 to 1.

1 / 5

Completeness

It answers neither "what does this skill do" (no actions) nor "when should Claude use it" (no Use-when clause); it is a persona narrative rather than a capability statement, fitting the anchor for missing both what and when.

1 / 5

Trigger Term Quality

Relevant keywords a user might say are present ("GraphQL APIs", "N+1 query problem", "deeply nested queries"), but common variations and synonyms (Apollo, federation, schema, resolvers, .graphql) are missing.

3 / 5

Distinctiveness Conflict Risk

GraphQL APIs at scale is a clear, fairly distinct niche with minimal conflict risk against unrelated skills, though the persona framing slightly weakens trigger clarity versus an explicit action statement.

4 / 5

Total

9

/

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.