Comprehensive toolkit for validating, linting, and testing GitHub Actions workflow files, custom local actions, and public actions. Use this skill when working with GitHub Actions YAML files (.github/workflows/*.yml), validating workflow syntax, testing workflow execution with act, or debugging workflow issues.
Overall
score
93%
Does it follow best practices?
Validation for skill structure
Discovery
100%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 is an excellent skill description that hits all the key criteria. It provides specific capabilities (validating, linting, testing), includes natural trigger terms users would actually say (GitHub Actions, workflow files, .yml), and explicitly states when to use it. The description is distinctive enough to avoid conflicts with other skills while being comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'validating, linting, and testing GitHub Actions workflow files, custom local actions, and public actions' - covers distinct capabilities clearly. | 3 / 3 |
Completeness | Clearly answers both what ('validating, linting, and testing GitHub Actions workflow files') AND when ('Use this skill when working with GitHub Actions YAML files...') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'GitHub Actions', 'workflow files', 'YAML files', '.github/workflows/*.yml', 'workflow syntax', 'act', 'debugging workflow issues' - includes file paths, tool names, and common user language. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific niche: GitHub Actions workflows, specific file paths (.github/workflows/*.yml), and unique tool reference (act). Unlikely to conflict with general YAML or CI/CD skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill with excellent actionability and workflow clarity. The mandatory 5-step process with explicit validation checkpoints ensures consistent behavior. The error-to-reference mapping table is particularly valuable. Minor verbosity in the worked example section and some redundancy between tables slightly reduces token efficiency.
Suggestions
Consider condensing the 'Complete Worked Example' section since it largely demonstrates concepts already explained in the error mapping table - a shorter example or reference to the mapping would suffice
The 'Reference Files Summary' table could be removed since the 'Error-to-Reference Mapping' table already provides this information with more context
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the complete worked example repeats information already covered in the error mapping table, and some sections like the overview could be tighter. The reference file summary table duplicates information available in the mapping table. | 2 / 3 |
Actionability | Excellent actionability with fully executable bash commands, complete YAML examples, specific error-to-reference mappings, and copy-paste ready code. The worked example shows exact inputs and outputs. | 3 / 3 |
Workflow Clarity | Outstanding workflow clarity with explicit 5-step process that must be followed, clear validation checkpoints (Step 3: Quote the Fix, Step 5: Provide Complete Summary), and explicit error recovery guidance. The error-to-reference mapping table provides clear decision points. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview, quick start, and detailed sections. References to external files (references/*.md) are one level deep and clearly signaled in a mapping table. Content is appropriately split between the main skill and reference files. | 3 / 3 |
Total | 11 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Install with Tessl CLI
npx tessl i pantheon-ai/github-actions-validatorReviewed
Table of Contents