skill-tester-ci
Validates all CI skills in this repo. Checks Agent Skills spec compliance, gh-aw workflow compilation, permission correctness, and structural conventions. Use when CI skills have been added or modified and you want to verify they compile and conform before committing.
What this skill does
# Skill Tester CI Validates all CI skills (`*-ci`) in this repo. Runs spec validation, compiles gh-aw workflows, and checks CI-specific conventions. ## When to Use - After adding or modifying a CI skill - After upgrading `gh-aw` to a new version (API changes may break workflows) - Before committing CI skill changes - Before submitting the plugin for Anthropic review ## Prerequisites - `gh-aw` CLI installed (`gh extension install github/gh-aw`) - `python3` with `pyyaml` installed - `quick_validate.py` available at `.claude/skills/skill-creator/scripts/` ## Checks ### 1. Anthropic Spec Validation Run `quick_validate.py` on every CI skill: ```bash for d in skills/*-ci/; do python3 .claude/skills/skill-creator/scripts/quick_validate.py "$d" done ``` ### 2. Workflow Example Compilation Extract workflow blocks from each CI skill's `references/workflow-example.md` and compile with `gh aw compile`: ```bash # Extract markdown code blocks with frontmatter # Copy to temp .github/workflows/ # Run: gh aw compile ``` **Pass criteria:** Zero compilation errors. Warnings are reported but don't fail. ### 3. Permission Checks CI workflows in strict mode must NOT use write permissions directly. Verify: - No `issues: write` (use `safe-outputs: add-comment` instead) - No `pull-requests: write` (use `safe-outputs: create-pull-request-review-comment` instead) - No `contents: write` unless the workflow creates files (eval-creator create mode) - Required read permissions present for declared toolsets ### 4. Structural Checks | Check | Rule | Severity | |-------|------|----------| | Has `references/workflow-example.md` | Required for all CI skills | Error | | Workflow example has frontmatter block | At least one `` ```markdown `` block with `---` | Error | | Name matches folder | Frontmatter `name` == directory name | Error | | Description mentions gh-aw | CI skills should reference gh-aw | Warning | | Has corresponding interactive skill | `foo-ci` should have a `foo` counterpart | Warning | ### 5. Cross-Workflow Validation For workflows that use `call-workflow`: - Verify the target workflow exists and has `workflow_call` in its `on:` section - Verify the target's inputs match what the caller provides ## Output Format ```markdown ## CI Skill Test Results **Date:** YYYY-MM-DD **gh-aw version:** vX.Y.Z **Skills tested:** N **Passed:** N **Compile errors:** N **Spec failures:** N ### Compilation Results - [skill-name]: ✓ compiled (N KB) | ✗ error: [message] ### Spec Results - [skill-name]: ✓ valid | ✗ [error] ### Permission Issues - [skill-name]: [issue] ``` ## Running Invoke manually: ``` /skill-tester-ci ``` Or run the script directly: ```bash bash skills/skill-tester-ci/scripts/run-tests.sh ``` ## What This Skill Does NOT Do - Does not test interactive skills (use `skill-tester` for those) - Does not execute workflows against real repos — only compiles them - Does not modify skills — reports findings only - Does not test workflow runtime behavior — compilation validates structure and permissions only
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.