all publishers

EONRaider

@eonraider source repo

2 published skills

  1. ▌
    Creating Skills · eonraider bundle
    Create new Claude Skills from scratch, or validate, secure, and evaluate ones already drafted. Use when the user wants to build a skill, package a repeated workflow into something Claude can reuse, or asks whether something "should be a skill" — this runs a decision gate first (skill vs. CLAUDE.md vs. AGENTS.md vs. MCP vs. subagent vs. plugin) and checks whether something already covers the request before writing anything new. Also use for validating a SKILL.md's frontmatter, gerund naming, or portable-field compliance; scanning a skill for leaked secrets or unsafe patterns; benchmarking a skill's task-success rate with and without it enabled; or optimizing a description for triggering accuracy. Covers Claude Code, Claude.ai, Cowork, Claude Tag, and Messages API authoring, targeting the cross-vendor agentskills.io spec by default. Use even without the word "skill" — "turn this into something Claude can reuse", "why isn't my skill triggering", "is this safe to publish", "does this frontmatter look right".
    4 installs
  2. ▌
    Drafting Changelog Entries · eonraider bundle
    Draft a CHANGELOG.md entry for SkillArtisan by cross-referencing what was actually built against the master spec's Gap Table, so nothing gets marked closed that isn't verifiably true of the repo. Use when a build session (or a stage/prompt) has finished and it's time to record what shipped, when asked to "update the changelog," "draft release notes," "write up what we just built," or "check what's still open," or when preparing a version bump (major = v-stage boundary per this project's semver interpretation, minor = new capability within a stage, patch = a fix). Use even without the word "changelog" — "what's left before this ships," "summarize this session for the log," "did we close row 12."
    4 installs