CtrlK
BlogDocsLog inGet started
Tessl Logo

civic-skill

Submit compact CIViC GraphQL requests for cancer variant interpretation schema inspection and targeted evidence retrieval. Use when a user wants concise CIViC summaries

70

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

A tight, fully executable script-interface skill: the body documents the stdin contract, output shapes, error codes, and a runnable example with zero padding. The only trimmable content is mild rule duplication between the two rule sections.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence (stdin contract, field lists, error codes as terse bullets), but "Keep selection sets narrow and start with schema or targeted entity queries" and "Prefer sanity, schema, and targeted evidence queries over broad graph dumps" duplicate each other across the Operating rules and Execution behavior sections. This matches the 4 anchor (efficient, minor instances that could be trimmed) rather than the 5 anchor's every-token-earns-its-place.

4 / 5

Actionability

The body provides a copy-paste-ready executable command (echo '{"query":"query { __typename }"}' | python scripts/civic_graphql.py), an explicit stdin JSON contract with required and optional fields, and two concrete example payloads. This matches the 5 anchor: fully executable examples covering the common cases.

5 / 5

Workflow Clarity

This is a simple single-task skill (run one script with a JSON payload) and the single action is unambiguous, with failure modes documented via error codes. Per the simple-skill exception this scores 5; the operations are read-only GraphQL queries, so no destructive/batch validation cap applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (confirmed: the bundle contains only scripts/civic_graphql.py, which exists), and is organized into clear headed sections (Operating rules, Execution behavior, Input, Output, Execution, References). Per the no-external-references exception this scores 5.

5 / 5

Total

19

/

20

Passed

Description

78%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.

A strong, specific description in third-person voice with concrete actions and an explicit trigger clause. Its main weakness is that the "Use when" clause is narrower than the stated capabilities and lacks a few natural trigger synonyms.

Suggestions

Broaden the 'Use when' clause to mirror the full capability set, e.g. 'Use when a user wants concise CIViC summaries, evidence items, or variant interpretation details, or needs to inspect the CIViC GraphQL schema.'

Add natural trigger synonyms such as 'CIViC evidence items', 'clinical variant curation', or 'CIViC API' to improve keyword coverage.

Mention the default output form (concise markdown summaries vs raw JSON) in the description so users know what to expect from the what-clause.

DimensionReasoningScore

Specificity

"Submit compact CIViC GraphQL requests", "schema inspection", and "targeted evidence retrieval" are several concrete actions with only minor coverage gaps. It is not a 5 because coverage is not comprehensive (e.g., no mention of summarizing or returning markdown output), and not a 3 because it lists more than 1-2 specific actions.

4 / 5

Completeness

It has both a clear "what" and an explicit "Use when a user wants concise CIViC summaries" trigger. The "when" could be more specific and broader — it only covers summaries, not schema inspection or evidence retrieval — matching the 4 anchor rather than the fully concrete 5.

4 / 5

Trigger Term Quality

Natural terms like "CIViC", "GraphQL", "cancer variant interpretation", and "CIViC summaries" give good keyword coverage. A few natural variations are missing (e.g., "CIViC evidence items", "clinical variant curation", "CIViC API"), so it falls just short of the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

"CIViC GraphQL" names a clear niche with distinct triggers; it is unlikely to fire for unrelated skills. This matches the 5 anchor (clear niche, minimal conflict risk) and is clearly above the 4 anchor's "minor overlap risk with closely related skills".

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
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.