CtrlK
BlogDocsLog inGet started
Tessl Logo

readme-doctor

Audit a GitHub repo's README against best-practice patterns and produce a prioritized punch list of fixes. Runs a structured review covering hero presence, install-to-first-success length, "what is this in one sentence" clarity, audience-jargon match, scannability, and drift signals (stale versions, dead links, badge sprawl). Read-only diagnostic; opens a PR only when the user explicitly asks.

69

Quality

83%

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

SKILL.md
Quality
Evals
Security

Low

Low-risk findings.

2 low severity findings. Worth noting, but not necessarily harmful.

Low

W011: Third-party content exposure detected (indirect prompt injection risk).

What this means

The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.

Why it was flagged

The skill explicitly accepts a GitHub URL and performs `gh repo view` + shallow clone and scans README text, recent commits, file tree, and GitHub signals (see SKILL.md §1.2–1.3), meaning it ingests arbitrary public GitHub repos (user-generated/untrusted content) and uses that content to drive classification, scoring, and potential edits — enabling indirect prompt injection.

Report incorrect finding
Low

W012: Unverifiable external dependency detected (runtime URL that controls agent).

What this means

The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.

Why it was flagged

The skill explicitly fetches a user-supplied GitHub repository URL at runtime (e.g., https://github.com/owner/repo or git@github.com:owner/repo.git via `gh repo view` + clone) and injects the README/manifest/file-tree content into the audit prompts, so external repo content directly controls the model's inputs.

Repository
livlign/claude-skills
Audited
Security analysis
Snyk

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.