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

How to publish a linted skill to Skillmd.com with Skillmd

Dry-run and publish a skill to the registry, with publishing blocked on lint errors.

Credentials. Publishing needs a Skillmd.com token from your account, so keep that token private and do not paste it into shared logs or agent prompts.

Who it is forA skill author who has a finished skill and wants other people to find and install it from Skillmd.com.

The problemPublishing a skill that fails format checks would put a broken skill in front of users, and the author needs to check before going live.

The outcomeThe skill gets a registry page with a safety verdict, an install command for every agent, and a README badge.

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. Run skillmd login and paste the token from your Skillmd.com account.
  2. Run skillmd lint ./my-skill and fix any errors it reports. (inferred, check the README)
  3. Run skillmd publish ./my-skill --dry-run to preview the publish without sending it.
  4. Run skillmd publish ./my-skill to publish, then open the new skill page on Skillmd.com.

Prompt for your agent

Use the skillmds CLI from the skillmds repo to lint <path-to-skill> and then run `skillmd publish <path-to-skill> --dry-run`. Report any lint errors and the dry-run output. Verify that the dry run succeeds before running the real publish.

Caveat. The README says publishing is blocked on lint errors and runs the same lint and scan as the CLI, but it does not state the account requirements beyond the token.

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