skill
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".
What this skill does
# Skill — The Sundial Meta-Skill Find, install, create, improve, and publish skills via [Sundial Hub](https://sundialhub.com). ## 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: ```bash 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: ```bash npx sundial-hub add --yes --global AGENT_FLAG author/skill-name ``` For project install: ```bash 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/validate_skill.sh PATH_TO_SKILL ``` 7. 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 4. Present findings as a structured report with the score and specific change recommendations 5. After user approval, implement the suggested changes ## Publish a Skill ### Check Authentication ```bash npx sundial-hub auth status ``` If not authenticated, prompt the user to run: ```bash npx sundial-hub auth login ``` They can also manage tokens at https://sundialhub.com/settings#tokens ### Validate First ```bash 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: ```bash npx sundial-hub push SKILL_PATH --version VERSION --changelog "MESSAGE" --visibility public --categories Cat1 Cat2 ``` For an existing skill update: ```bash 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/validate_skill.sh SKILL_PATH` 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)
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.