github-actions-starter
Github Actions Starter - Auto-activating skill for DevOps Basics. Triggers on: github actions starter, github actions starter Part of the DevOps Basics skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/01-devops-basics/github-actions-starter/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a title and category label with no substantive content. It fails to describe any concrete capabilities, lacks natural trigger terms users would employ, and provides no guidance on when Claude should select this skill. It reads like auto-generated boilerplate rather than a useful skill description.
Suggestions
Add concrete actions the skill performs, e.g., 'Creates starter GitHub Actions workflow files for CI/CD pipelines, sets up build/test/deploy configurations, and generates .yml workflow templates.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to set up GitHub Actions, create CI/CD pipelines, configure automated workflows, or generate .github/workflows YAML files.'
Remove the duplicate trigger term ('github actions starter' is listed twice) and replace with varied natural phrases users would actually say, such as 'CI pipeline', 'automated testing', 'deploy workflow', 'GitHub workflow YAML'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It says 'Github Actions Starter' and 'Auto-activating skill for DevOps Basics' but never describes what it actually does — no verbs like 'creates', 'configures', 'generates', etc. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause, and the description provides no information about the skill's capabilities beyond its name. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'github actions starter' repeated twice. These are not natural phrases a user would say — users would more likely say 'set up CI/CD', 'create a GitHub Actions workflow', 'CI pipeline', '.github/workflows', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Github Actions' provides some domain specificity that distinguishes it from generic DevOps skills, but the lack of concrete actions means it could overlap with any GitHub Actions-related skill. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no actual technical content about GitHub Actions. It contains only meta-descriptions of what the skill would do, repeated trigger phrases, and generic boilerplate. It provides zero actionable value—no workflow YAML examples, no CI/CD configuration guidance, and no concrete steps for setting up GitHub Actions.
Suggestions
Add a concrete, minimal GitHub Actions workflow YAML example (e.g., a basic CI pipeline that runs tests on push) that is copy-paste ready.
Replace the 'Capabilities' and 'Example Triggers' boilerplate sections with actual step-by-step instructions for common GitHub Actions tasks (e.g., setting up a workflow file, configuring triggers, adding secrets).
Include validation steps such as how to verify a workflow runs correctly (checking the Actions tab, using `act` for local testing, reviewing logs for common errors).
Add references to advanced topics (matrix builds, reusable workflows, caching) either inline or via clearly signaled external files to support progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the trigger phrase 'github actions starter' excessively, and provides zero actual technical content about GitHub Actions. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no YAML workflow examples, no specific steps. The entire skill describes what it would do rather than providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequences, no validation checkpoints. The skill merely claims it 'provides step-by-step guidance' without actually containing any. | 1 / 3 |
Progressive Disclosure | There is no meaningful content to organize, no references to supporting files, and no bundle files exist. The sections are superficial headings over empty platitudes rather than structured, navigable content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
13d35b8
- 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.