CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

google-docs-md

Export Google Docs as clean markdown via native URL parameter. No auth needed for public docs. Use when fetching Google Doc content for vault ingestion, runbook building, or any doc-to-markdown pipeline.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/google-docs-md/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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, highly actionable single-file skill: every command is executable and the organization is clean. The main weaknesses are duplicated guidance between the intro and 'When to Use', and a batch pattern with no verification or error-recovery steps.

Suggestions

Add validation to the batch loop: check the HTTP status and output (e.g. fail on non-200, skip/flag empty or HTML error responses) so failed fetches are caught instead of silently producing bad files.

Merge or trim the 'When to Use' section — its defuddle/scraping preference and quality claims duplicate the intro paragraph.

Clarify the 'gog' mention in Limitations — it is referenced as the OAuth path for private docs but never explained, leaving the private-doc workflow without a concrete fallback.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence, with no padding explaining concepts Claude already knows. Minor over-explanation/dupe remains: the 'When to Use' section repeats the intro's claim ('Always prefer this over defuddle/scraping' vs 'better than defuddle, jina, or any scraping tool'), which keeps it below the 5 anchor.

4 / 5

Actionability

Fully executable, copy-paste-ready commands: the export URL pattern, a working doc-ID extraction grep with a real example ID, public and authenticated curl invocations, and a complete batch loop. The common cases are all covered concretely.

5 / 5

Workflow Clarity

The single-fetch sequence (extract ID, build export URL, curl -L) is clear, but the batch loop performs a destructive/risky batch operation with no validation — no HTTP status check, no empty-output or error-page detection, and no retry/feedback loop. Per the guideline capping batch operations without validation, this cannot score above 3.

3 / 5

Progressive Disclosure

A simple, single-purpose skill with no bundle files needed; the content is appropriately organized into short, well-labeled sections (URL pattern, ID extraction, fetching, formats, batch, limitations) with no inlined content that belongs in separate files and easy navigation.

5 / 5

Total

17

/

20

Passed

Description

73%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, concise description with an explicit 'Use when...' clause, third-person voice, and a well-defined niche. Main gaps are the single-action specificity and trigger terms that lean toward niche pipelines rather than the natural phrases a user would say when sharing a Google Doc link.

Suggestions

Broaden the 'Use when' clause with natural user-phrase triggers, e.g. 'Use when the user shares a Google Docs link or asks to convert a Google Doc to markdown'.

Add one or two concrete capability keywords (e.g. 'convert Google Doc to markdown', 'fetch Google Docs as markdown') to strengthen trigger-term coverage for users who say 'convert' rather than 'export'.

Consider briefly mentioning what the skill handles (tables, links, formatting) to raise specificity beyond a single action.

DimensionReasoningScore

Specificity

The description names the domain ('Google Docs') and one concrete action/mechanism ('Export... as clean markdown via native URL parameter'), but does not list several specific actions. It fits the '1-2 concrete actions, not comprehensive' anchor; it is not a 4 because no broader set of capabilities is enumerated.

3 / 5

Completeness

Both 'what' ('Export Google Docs as clean markdown via native URL parameter. No auth needed for public docs.') and 'when' ('Use when fetching Google Doc content for vault ingestion, runbook building, or any doc-to-markdown pipeline') are explicit. Not a 5 because the 'when' triggers skew niche (vault ingestion, runbook building) and omit natural user-phrase triggers like 'when the user shares a Google Docs link'.

4 / 5

Trigger Term Quality

Good keyword coverage: 'Google Docs', 'Google Doc content', 'markdown', 'export', 'doc-to-markdown pipeline'. A few natural terms users would say are missing, e.g. 'convert to markdown' or 'Google Drive link', so it falls short of the comprehensive-synonyms anchor at 5 but is clearly above the 3 anchor ('some relevant keywords, missing common variations').

4 / 5

Distinctiveness Conflict Risk

Clear niche — exporting Google Docs specifically as markdown — with distinct trigger phrases and no meaningful overlap with generic document or scraping skills.

5 / 5

Total

16

/

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.

Validation — 15 / 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

joelhooks/joelclaw

Path

skills/google-docs-md/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.