CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

citation-fixer

Audit and fix citation formatting across brain pages. Ensures every fact has an inline [Source: ...] citation matching the standard format. Extended in v0.25.1: scans for broken tweet/post references that lack actual URLs and resolves them via the host's X / Twitter API integration.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is citation-fixer in garrytan/gbrain

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 highly actionable, well-sequenced body with strong validation and error-recovery loops appropriate to a mutating batch skill — the tweet-resolution pipeline is fully executable with concrete query patterns, before/after examples, and failure handling. The main costs are repeated v0.25.1 version annotations, a redundant empty Output Format stub kept only for a conformance test, and inlining a sub-procedure that belongs in a reference file.

Suggestions

Remove the trailing "## Output Format" stub section — meta-content that exists only to pass a test wastes context and duplicates the real Output format section.

Replace the six scattered "(v0.25.1)" annotations with a single note (or a small changelog/deprecated section), so the operational steps read cleanly without version archaeology.

Move the tweet resolution pipeline (Steps 1-5) into a reference file (e.g., references/tweet-resolution.md) and keep a one-line pointer in the main phases, keeping SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

Mostly efficient operational guidance with no padding explaining concepts Claude already knows, but it includes unnecessary material: the "(v0.25.1)" version annotation is repeated six times throughout (and per the rubric, version numbers outside a deprecated/old-patterns section penalize conciseness), and the trailing "## Output Format" section is an empty stub whose stated purpose is to satisfy a conformance test ("The literal section header here exists for the conformance test"), adding pure noise. Not 4: these are not merely minor trims — the version tags and the duplicated stub section are several instances of content that could be removed outright.

3 / 5

Actionability

Fully executable guidance throughout: exact search query patterns (`from:<handle> "<exact quote fragment>"`), a deterministic URL construction rule (`https://x.com/<handle>/status/<tweet_id>`), concrete before/after citation examples, a copy-paste bash loop for finding candidate pages, an exact report template, and a JSON state-file shape. The one abstraction — delegating the API call to "whatever X integration the host has configured" — is explicitly justified since the host environment varies. Not 4: the common cases are covered with copy-paste-ready commands, templates, and examples.

5 / 5

Workflow Clarity

The sequence is explicit (Phases 1-5, a 5-step tweet resolution pipeline, batch mode with priority order) and — critical for a mutating batch skill — validation and feedback loops are present: Step 4 requires confirming the text matches before patching, the anti-patterns mandate sample-checking before bulk fixes, `revision_conflict` triggers re-read/re-apply/continue, batch-commits every 10-20 pages bound partial failure, and an interrupted commit resumes from the last committed page. The destructive/batch cap of 3 does not apply because validation is explicit. Not 4: checkpoints are not merely present but include error-recovery loops and a failure-mode section covering specific error codes.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the body is well-organized with clear section headers and clearly signaled one-level-deep links to conventions files (`conventions/quality.md`, `../_output-rules.md`, `../conventions/agent-operator-protocol.md`, `conventions/test-before-bulk.md`) at the top and inline where relevant. Not 5: the tweet resolution pipeline (~60 lines of sub-procedure) is inline content that would fit naturally in a reference file, and the duplicate trailing "## Output Format" stub is an organization gap that hurts navigation.

4 / 5

Total

17

/

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.

A specific, well-scoped description with concrete actions and strong distinctiveness, written in appropriate third-person imperative voice. Its main weakness is that the 'when to use' guidance is relegated to separate frontmatter fields instead of appearing in the description itself, which caps completeness.

Suggestions

Fold a 'Use when...' clause into the description itself (e.g., 'Use when the user asks to fix citations, run a citation audit, or repair broken tweet/post references') rather than relying on the separate when_to_use and triggers fields.

Add a few natural synonyms users might say — 'sources', 'attributions', 'broken links' — to broaden trigger-term coverage.

Drop the 'Extended in v0.25.1' version framing from the description; describe current capabilities directly without version archaeology.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Audit and fix citation formatting", "Ensures every fact has an inline [Source: ...] citation matching the standard format", "scans for broken tweet/post references that lack actual URLs and resolves them via the host's X / Twitter API integration" — covering the skill's full scope as documented in the body. Not 4: coverage of the skill's capabilities is comprehensive, with no meaningful gaps between the description and the actual feature set.

5 / 5

Completeness

The "what" is clearly and concretely answered (audit citations, fix formatting, resolve broken tweet references via X API), but the description text itself contains no "Use when..." clause or equivalent trigger guidance — the when-guidance lives in separate frontmatter fields (`triggers`, `when_to_use`) rather than the description. Per the rubric, a missing 'Use when...' clause caps completeness at 3. Not 4: the 'when' is not merely implicit in the description, it is absent from it.

3 / 5

Trigger Term Quality

Good keyword coverage: "citation", "citation formatting", "fix", "tweet/post references", "X / Twitter", "URLs" — natural phrases a user would say when needing this skill. Not 5: common synonyms and variations like "sources", "attributions", "references", or "broken links" are missing. Not 3: coverage goes well beyond a couple of generic keywords and includes the domain's natural vocabulary.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct — inline [Source: ...] citation compliance on brain pages plus tweet-reference resolution via X API — and unlikely to fire for unrelated skills. Not 4: the triggers are narrowly scoped to citation work and the domain-specific [Source: ...] convention, leaving minimal overlap even with closely related skills.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 3 suspicious

Warning

Total

14

/

16

Passed

Repository

garrytan/gbrain

Path

plugin/skills/citation-fixer/SKILL.md

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.