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
Quality
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 severely lacking in substance. It reads as auto-generated boilerplate with no actual explanation of capabilities, use cases, or natural trigger terms. The repeated trigger term and category label provide minimal value for skill selection.
Suggestions
Add specific capabilities: describe what the skill does (e.g., 'Creates GitHub Actions workflow files, configures CI/CD pipelines, sets up automated testing and deployment').
Add a 'Use when...' clause with natural trigger terms like 'CI/CD', 'workflow', 'automate tests', 'GitHub pipeline', 'deploy automatically', '.github/workflows'.
Remove the redundant trigger term repetition and replace with varied, natural phrases users would actually say when needing GitHub Actions help.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Github Actions Starter' and 'Auto-activating skill for DevOps Basics' are labels, not capabilities. There's no indication of what this skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' entirely - there are no capabilities listed. The 'when' is technically present via 'Triggers on' but the triggers are unnatural and the description lacks any 'Use when...' guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'github actions starter' repeated twice, which is not a natural phrase users would say. Missing natural terms like 'CI/CD', 'workflow', 'pipeline', 'automate builds', or 'deploy'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Github Actions' provides some specificity to the GitHub Actions domain, but 'DevOps Basics' is vague and could overlap with other CI/CD or deployment skills. The lack of specific capabilities makes it harder to distinguish. | 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 content is entirely boilerplate with no actionable information about GitHub Actions. It describes capabilities abstractly without providing any concrete code examples, workflow YAML, commands, or specific guidance. The content could apply to virtually any topic by swapping the skill name.
Suggestions
Add a concrete GitHub Actions workflow YAML example (e.g., a basic CI workflow for running tests)
Include specific commands for common tasks like triggering workflows, viewing logs, or debugging failures
Provide a step-by-step workflow for creating a new GitHub Action from scratch with validation checkpoints
Reference external files or documentation for advanced topics like matrix builds, secrets management, or reusable workflows
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about GitHub Actions. Phrases like 'automated assistance' and 'industry best practices' are filler that Claude already understands. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The skill describes what it does abstractly but never shows how to actually create or configure a GitHub Action. | 1 / 3 |
Workflow Clarity | No steps, sequences, or workflows are defined. The content only lists vague capabilities without any process for accomplishing GitHub Actions tasks. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to detailed materials, examples, or supporting documentation. No structure for discovery or navigation. | 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
994edc4
- 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.