DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to check every skill in a repo on each pull request with Skillmd

Add a GitHub Action that lints all skills and posts results to GitHub Code Scanning.

Who it is forA maintainer of a git repository full of skills who wants broken skills caught in pull requests before merge.

The problemSkills in a shared repo can drift from the format, and reviewers may not notice formatting or safety issues in each change.

The outcomeEvery pull request shows lint findings from GitHub Code Scanning, so problems are visible during review.

What you need first

  • Node.js with npm, since the README uses npm and npx commands
  • A terminal on your machine or in CI
  • A skill folder containing a SKILL.md file (for lint and publish use cases)
  • A skillmd.com account and token (only for publishing)

Steps

  1. Create a workflow file in your repo, such as .github/workflows/skillmd.yml.
  2. Add a job step with uses: skillmds/skillmd/action@v1 and set with: path: . to scan the whole repo. (inferred, check the README)
  3. Give the job permission to upload SARIF results so Code Scanning accepts them, following the full example in examples/github-action.yml. (inferred, check the README)
  4. Open a pull request that changes a SKILL.md file and check the Code Scanning results on that pull request.

Prompt for your agent

Add the skillmds/skillmd/action@v1 step with path set to '.' to the CI workflow in <repo-path>, using examples/github-action.yml from the skillmds repo as the template. Confirm the workflow file is valid YAML and report which skills the action lints.

Caveat. The README says the action uploads results to GitHub Code Scanning but does not list the exact permissions the workflow needs, so check examples/github-action.yml for the required settings.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page