CtrlK
BlogDocsLog inGet started
Tessl Logo

golang-continuous-integration

GitHub Actions CI/CD pipeline configuration for Golang projects — workflow files for test, lint, SAST, coverage and vulnerability-scan jobs, Dependabot and Renovate config files, GoReleaser release pipelines, Docker build/push, repository security settings, and AI-driven PR review. Use when setting up or improving Go project CI, writing or fixing `.github/workflows/*.yml`, adding a linter or security scanner as a pipeline job, wiring automated dependency-update bots, or adding quality gates. Covers wiring tools into a pipeline, not the analysis they perform: do NOT use for choosing or interpreting security findings (→ See `samber/cc-skills-golang@golang-security` skill) or for choosing, upgrading, or auditing dependency versions (→ See `samber/cc-skills-golang@golang-dependency-management` skill).

72

Quality

89%

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

Quality

Content

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

The body is a well-structured overview that delegates executable workflow content to a real, complete bundle of asset files with clear navigation. It is actionable and token-efficient, with only minor room to tighten prose and add an explicit post-generation validation step.

Suggestions

Trim soft justifications like 'Renovate is a more mature and configurable alternative...' to the factual advantages list to improve conciseness.

Add an explicit post-generation validation step (e.g. 'run the workflow on a PR or act locally, then fix failures') to close the workflow_clarity feedback loop.

Inline the minimal .golangci.yml starter or link directly to the specific section of the golang-lint skill so the linting path is fully self-contained.

DimensionReasoningScore

Conciseness

The body is largely lean — it delegates full workflow YAML to asset files and keeps prose to decisions and flags — but a few explanatory sentences (e.g. 'Renovate is a more mature and configurable alternative to Dependabot...') could be trimmed. Not a 5 because minor over-explanation remains; not a 3 because it largely assumes Claude's competence.

4 / 5

Actionability

Provides concrete commands (`go test -race`, `-shuffle=on`, `git diff --exit-code`, install commands, `npx skills add ...`) and a matrix-adaptation table, and points to complete executable workflow files. Not a 5 because some guidance delegates detail to other skills (e.g. .golangci.yml config) leaving minor gaps.

4 / 5

Workflow Clarity

Setup mode gives an explicit ordering (test → lint → security → release) and Improve mode gives a read-gap-propose sequence, with `git diff --exit-code` as a validation checkpoint and security warnings throughout. Not a 5 because there is no explicit validate-the-generated-pipeline feedback loop after generation.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview (Quick Reference table + per-stage sections) with well-signaled one-level-deep links to real asset files (`see [test.yml](./assets/test.yml)`, etc.) and repo-security.md; all referenced paths exist in the bundle and content is appropriately split.

5 / 5

Total

17

/

20

Passed

Description

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

The description is a strong, comprehensive statement that clearly scopes what the skill does, when to invoke it, and where its boundaries lie relative to sibling skills. It avoids vague fluff and uses concrete, natural trigger language.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the domain — 'workflow files for test, lint, SAST, coverage and vulnerability-scan jobs, Dependabot and Renovate config files, GoReleaser release pipelines, Docker build/push, repository security settings, and AI-driven PR review' — matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both 'what' (the pipeline-configuration capabilities) and 'when' (a 'Use when...' clause with concrete triggers), plus anti-trigger boundary guidance, matching the top anchor.

5 / 5

Trigger Term Quality

Natural trigger phrases users would say — 'setting up or improving Go project CI, writing or fixing `.github/workflows/*.yml`, adding a linter or security scanner as a pipeline job, wiring automated dependency-update bots, or adding quality gates' — include a file-extension wildcard and broad synonym coverage.

5 / 5

Distinctiveness Conflict Risk

A clear Go CI/CD niche with explicit 'do NOT use for...' pointers to the golang-security and golang-dependency-management skills, minimizing conflict risk.

5 / 5

Total

20

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository
samber/cc-skills-golang
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.