graphql-subscription-setup
Graphql Subscription Setup - Auto-activating skill for API Development. Triggers on: graphql subscription setup, graphql subscription setup Part of the API Development skill category.
34
3%
Does it follow best practices?
Impact
87%
0.98xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/15-api-development/graphql-subscription-setup/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is extremely minimal—essentially just a title and category label repeated with no substantive content. It lacks concrete actions, natural trigger terms, and any explicit guidance on when Claude should select this skill. It would be nearly indistinguishable from other API-related skills in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures GraphQL subscription resolvers, sets up WebSocket transport, implements pub/sub patterns for real-time data streaming.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about real-time updates, GraphQL subscriptions, WebSocket setup, live data feeds, or pub/sub with GraphQL.'
Remove the duplicate trigger term ('graphql subscription setup' is listed twice) and expand with varied natural language terms users might actually use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('GraphQL Subscription Setup') but lists no concrete actions like 'configure WebSocket connections', 'define subscription resolvers', or 'set up pub/sub handlers'. It is essentially just a title repeated. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title and has no explicit 'when to use' clause. There is no 'Use when...' guidance, and the 'what' is essentially absent beyond the skill name. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'graphql subscription setup' repeated twice. It misses natural variations users would say like 'real-time updates', 'WebSocket', 'pub/sub', 'subscription resolver', 'live data', or 'GraphQL subscriptions'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'GraphQL Subscription' is somewhat specific and narrows the domain compared to generic API skills, but without concrete actions or clear triggers, it could still overlap with general GraphQL or API development skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no substantive content. It contains only meta-descriptions of what it claims to do without any actual instructions, code, or guidance for setting up GraphQL subscriptions. It fails on every dimension because it provides zero actionable information.
Suggestions
Add concrete, executable code examples showing GraphQL subscription setup (e.g., using Apollo Server with WebSocket transport, or graphql-ws library) with server and client code snippets.
Define a clear multi-step workflow: 1) Install dependencies, 2) Configure WebSocket server, 3) Define subscription schema, 4) Implement resolvers with PubSub, 5) Test the subscription—with validation at each step.
Remove all meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actual technical content that teaches how to implement GraphQL subscriptions.
Add references to related files or sections for advanced topics like authentication in subscriptions, scaling with Redis PubSub, or subscription filtering patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same information in different ways. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no commands, no specific steps for setting up GraphQL subscriptions. The content only describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The phrase 'step-by-step guidance' is promised but never delivered. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of vague descriptions with no references to detailed materials, no links to examples, and no structured navigation to deeper content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.