sundial-org/skills

skill

Find, install, create, improve, and publish AI agent skills through the Sundial ecosystem.

First seen Mar 29, 2026

Installation

$ npx skills add sundial-org/skills --skill skill

Summary

  • Find, install, create, improve, and publish AI agent skills through the Sundial ecosystem.
  • Use when the user wants to find or search for skills, install a skill, create a new skill, improve or evaluate an existing skill, or publish a skill to Sundial Hub.
  • Trigger phrases include "find a skill", "install skill", "create a skill", "make a skill", "improve this skill", "evaluate skill", "publish skill", "push skill", "search for skills".

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from sundial-org/skills · top by installs.

npx skills add sundial-org/skills

Browse all from sundial-org/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 151
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code cursor windsurf

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,856 B
  • docs SUMMARY.md 451 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Skill — The Sundial Meta-Skill

Find, install, create, improve, and publish skills via Sundial Hub.

Agent Detection

Detect the current agent from the skill's load path to set the correct CLI flag:

  • .claude/ in path → --claude (default)
  • .cursor/ in path → --agent cursor
  • .windsurf/ in path → --agent windsurf
  • Other → --claude

Store the detected flag as AGENT_FLAG for use in CLI commands below.

Find & Install Skills

Searching

Run:

npx sundial-hub find "QUERY" --json --limit 10

Parse the JSON output array. Each result contains: name, author, description, installs, safety, url.

Present results as a numbered list:

1. author/skill-name — Description (installs: N, safety: LEVEL)
   https://sundialhub.com/skills/author/skill-name
2. ...

If no results: "No skills found. Browse all at https://sundialhub.com";

Installing

Ask the user: project scope (local to this project) or global scope (available everywhere)?

For global install:

npx sundial-hub add --yes --global AGENT_FLAG author/skill-name

For project install:

npx sundial-hub add --yes AGENT_FLAG author/skill-name

After install, show the skill's hub page URL.

Create a Skill

  1. Ask the user what the skill should do and gather concrete usage examples
  2. Ask: project scope or global scope?
  3. Read [references/skill-creation-guide.md](references/skill-creation-guide.md) for full guidance on skill anatomy, frontmatter spec, body writing, and design patterns
  4. Create the skill directory with SKILL.md containing proper frontmatter (name + description) and markdown body
  5. Add any needed scripts/, references/, or assets/ subdirectories
  6. Validate by running:

``bash bash scripts/validateskill.sh PATHTO_SKILL ``

  1. Tell the user: "Publish when ready using the publish workflow below"

For workflow patterns, also consult [references/workflows.md](references/workflows.md) and [references/output-patterns.md](references/output-patterns.md).

Improve a Skill

  1. Locate the SKILL.md to evaluate
  2. Read [references/improvement-rubric.md](references/improvement-rubric.md) for the full evaluation framework
  3. Evaluate the skill across three layers:

- Spec checks (7 pass/fail checks): SKILL.md exists, valid frontmatter, required fields, naming conventions, allowed fields, description constraints - Best practices (scored out of 100): line count, XML tags, README absence, description structure, actionable instructions, error handling, resource references, trigger phrases, examples - Expert review (qualitative): progressive disclosure, conciseness, freedom calibration

  1. Present findings as a structured report with the score and specific change recommendations
  2. After user approval, implement the suggested changes

Publish a Skill

Check Authentication

npx sundial-hub auth status

If not authenticated, prompt the user to run:

npx sundial-hub auth login

They can also manage tokens at https://sundialhub.com/settings#tokens

Validate First

bash scripts/validate_skill.sh PATH_TO_SKILL

All checks must pass before publishing.

Gather Publish Details

Ask the user for:

  • Version (semver, e.g. 1.0.0)
  • Changelog (brief description of changes)
  • Visibility: public or private
  • Categories (e.g. Coding, Writing, Productivity)

Push to Sundial Hub

For a new skill:

npx sundial-hub push SKILL_PATH --version VERSION --changelog "MESSAGE" --visibility public --categories Cat1 Cat2

For an existing skill update:

npx sundial-hub push SKILL_PATH --version VERSION --changelog "MESSAGE"

After publishing, show:

  • Published skill URL
  • Share URL (the .md link)

Troubleshooting

  • npx sundial-hub not found: Ensure Node.js 18+ is installed
  • Auth failures: Run npx sundial-hub auth login or check https://sundialhub.com/settings#tokens
  • Validation failures: Run bash scripts/validateskill.sh SKILLPATH and fix reported issues
  • Publish errors: Ensure all spec checks pass and you have write access

Links

  • Browse skills: https://sundialhub.com
  • CLI docs: npx sundial-hub --help
  • Skill spec: [references/skill-creation-guide.md](references/skill-creation-guide.md)