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.
34
0%
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
0%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 label with no substantive content. It fails to describe any concrete capabilities, lacks natural trigger terms users would use, and provides no guidance on when Claude should select this skill. It would be nearly useless for skill selection among multiple available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates starter GitHub Actions workflow files for CI/CD pipelines, sets up build and deploy configurations, generates .yml workflow templates.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about setting up GitHub Actions, CI/CD pipelines, workflow files, automated builds, or deployment automation.'
Include common keyword variations users might say, such as 'CI/CD', 'continuous integration', 'workflow YAML', 'GitHub pipeline', 'automated testing', '.github/workflows'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only names itself ('Github Actions Starter') and its category ('DevOps Basics') without describing what it actually does—no verbs like 'create', 'configure', 'set up workflows', etc. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no explanation of capabilities and no explicit 'Use when...' clause with trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'github actions starter' repeated twice. It misses natural user phrases like 'CI/CD', 'workflow', 'pipeline', 'deploy', 'build automation', '.yml workflow', or 'GitHub Actions'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any DevOps-related skill. Without specifying what it does (e.g., creating starter workflow files, configuring CI pipelines), it provides no clear niche to distinguish it from other DevOps or GitHub-related skills. | 1 / 3 |
Total | 4 / 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 shell with no actual technical content. It consists entirely of auto-generated boilerplate describing what the skill would do without providing any GitHub Actions knowledge, YAML examples, workflow configurations, or actionable guidance. It fails on every dimension because it contains no substantive content whatsoever.
Suggestions
Add a concrete starter workflow YAML example (e.g., a basic CI pipeline with checkout, install, test steps) that is copy-paste ready into `.github/workflows/`.
Include specific, actionable guidance on key GitHub Actions concepts: triggers (on: push/pull_request), job structure, common actions (actions/checkout, actions/setup-node), and secrets usage.
Add a workflow with validation steps, e.g., how to test a workflow locally with `act`, or how to debug failed runs using the Actions log output.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers') and replace with actual technical content—these sections describe the skill rather than teaching anything.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section describes rather than instructs, wasting tokens on information that provides no value. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no workflow YAML examples, no specific GitHub Actions configuration. The entire skill is vague descriptions like 'Provides step-by-step guidance' without actually providing any such guidance. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. For a skill about GitHub Actions (which inherently involves multi-step CI/CD workflows, YAML configuration, and validation), there are no sequences, no validation checkpoints, and no actual process described. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-descriptions with no structured technical content, no references to detailed files, and no meaningful organization. The sections are all about the skill itself rather than the domain knowledge. | 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
c8a915c
- 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.