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
Quality
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 essentially a placeholder that restates the skill name without providing meaningful content. It lacks concrete actions, natural trigger terms, and explicit usage guidance. The duplicated trigger term suggests auto-generation without human review.
Suggestions
Add specific actions the skill performs, e.g., 'Configure GraphQL subscription resolvers, set up WebSocket connections, implement pub/sub patterns for real-time data'
Include a 'Use when...' clause with natural trigger terms like 'real-time updates', 'live data', 'websocket', 'subscription resolver', 'pubsub'
Remove the duplicate trigger term and expand with variations users might actually say when needing this skill
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain 'graphql subscription setup' without describing any concrete actions. There are no specific capabilities listed like 'configure websocket connections', 'implement subscription resolvers', or 'handle real-time data streams'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond restating the title, and there is no explicit 'Use when...' clause or equivalent guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are duplicated ('graphql subscription setup' appears twice) and lack natural variations users might say like 'real-time graphql', 'websocket subscriptions', 'pubsub', 'live queries', or 'streaming data'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'graphql subscription' is somewhat specific to a particular technology, the lack of detail means it could overlap with general GraphQL skills or API development skills. The mention of 'API Development' category adds some context but doesn't fully distinguish it. | 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 content is essentially a template placeholder with no actual instructional value. It contains zero specific information about GraphQL subscriptions - no code examples, no library recommendations, no WebSocket setup guidance, no subscription resolver patterns. The entire content describes what the skill claims to do rather than actually doing it.
Suggestions
Add executable code examples showing GraphQL subscription setup with a specific library (e.g., Apollo Server, graphql-ws) including resolver implementation and client-side subscription handling
Include a clear workflow: 1) Configure WebSocket transport, 2) Define subscription type in schema, 3) Implement subscription resolver with pub/sub, 4) Test with GraphQL playground
Remove all meta-content about 'when to use' and 'example triggers' - replace with actual implementation patterns and common subscription use cases (real-time notifications, live data feeds)
Add validation steps such as testing subscription connections and verifying pub/sub message delivery
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about GraphQL subscriptions. It describes what the skill does in abstract terms rather than providing actual guidance, wasting tokens on meta-information Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific implementation details are provided. The content only describes that it 'provides step-by-step guidance' without actually providing any steps, making it completely non-actionable. | 1 / 3 |
Workflow Clarity | There is no workflow defined at all. No steps for setting up GraphQL subscriptions, no validation checkpoints, no sequence of operations - just vague claims about capabilities. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no references to detailed materials, no links to examples or advanced topics, and no meaningful structure beyond repetitive section headers. | 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
0c08951
- 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.