CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

apify-fix-git-connection

Repair an Apify Actor's broken Git connection - pushes to GitHub that no longer start a build, builds that fail to clone the repository, or a GitHub integration rejected as invalid or expired (for example after Apify API tokens were revoked). Use when a Git-sourced Actor stopped deploying from its repository.

Quality

95%

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

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

Excellent operational content: executable commands, diagnostic decision tables, explicit per-step exit criteria, and a closing end-to-end verification with feedback loops. The only structural note is that everything lives inline in SKILL.md with no reference files, which is defensible for a linear repair workflow but leaves progressive disclosure one notch below the top anchor.

DimensionReasoningScore

Conciseness

Every sentence carries non-obvious domain knowledge (e.g., "Console shows a token's value once, at creation", "The HTTPS form only clones public repositories") with zero padding and efficient diagnostic tables. Not below 5 because no section explains concepts Claude would already know or could be tightened without loss.

5 / 5

Actionability

Commands are copy-paste ready — full `apify api GET/POST/PUT` endpoints, `gh api` calls with jq projections, and exact Console click-paths ("Settings > Deploy keys > Add deploy key") — covering both diagnosis and repair. Anchor 5 fits: specific examples cover the common cases.

5 / 5

Workflow Clarity

Six sequenced steps each end in an explicit "Done when" checkpoint, diagnosis is table-driven, and the final step verifies four outcomes with explicit feedback loops ("A failed check sends you back to the step for its link") plus ask-before-deploy gates. Matches the anchor-5 pattern of validation, checklists, and error-recovery loops.

5 / 5

Progressive Disclosure

Sections are well-organized with a clear two-link mental model up front and appropriately ordered steps, and the content is a single linear workflow that needs no external files. Not 5 because the body is ~120 lines (above the under-50-line simple-skill exception) with no one-level-deep references or split content, which the anchor-5 example expects.

4 / 5

Total

19

/

20

Passed

Description

92%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 description: it names a niche capability, enumerates the concrete breakages it handles, includes an explicit and specific "Use when" trigger, and stays lean. The only gap is a handful of natural synonyms (e.g., webhook, auto-build) that would broaden trigger matching.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete failure modes — "pushes to GitHub that no longer start a build, builds that fail to clone the repository, or a GitHub integration rejected as invalid or expired" — giving comprehensive, concrete coverage of the repair scope with no padding.

5 / 5

Completeness

Explicitly answers both what ("Repair an Apify Actor's broken Git connection" with three concrete symptoms) and when ("Use when a Git-sourced Actor stopped deploying from its repository") with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("Apify Actor", "Git connection", "GitHub", "build", "clone", "push", "stopped deploying"), but a few terms users would plausibly say are missing, such as "webhook", "auto-build", or "integration"-adjacent synonyms. Not 5 because anchor 5 expects comprehensive synonym coverage; not 3 because the present terms are natural and varied rather than generic.

4 / 5

Distinctiveness Conflict Risk

The Apify Actor + Git-sourced deployment niche is highly specific with distinct trigger terms; minimal risk of firing for unrelated Git or CI skills.

5 / 5

Total

19

/

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

apify/agent-skills

Path

skills/apify-fix-git-connection/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.