Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

rhyanvargas

@rhyanvargas source repo

8 published skills

  1. ▌
    Skill Optimizer · rhyanvargas bundle
    Author and optimize Agent Skills for clarity, trigger accuracy, and token cost. Use when creating a new skill, editing SKILL.md, reviewing skill quality, optimizing descriptions, adding progressive disclosure, or when /optimize-skill is invoked. Do not use for README authoring, finding or installing third-party skills, general app feature specs, or DevOps strategy sessions.
    0
    installs
  2. ▌
    Readme Authoring · rhyanvargas bundle
    Create, update, review, or sync README.md files with evidence from the codebase, matched to audience (OSS, internal, personal, config). Use when writing or refreshing a README, documenting a package or CLI quick start, fixing stale/dense install docs, or when /update-readme is invoked. Do not use for changelogs, release notes, API reference generation, CONTRIBUTING-only or AGENTS.md-only edits, marketing landing copy, or optimizing Agent Skills.
    0
    installs
  3. ▌
    Supply Chain Gate · rhyanvargas bundle
    Triage Socket / supply-chain PR failures, decide merge vs block, and harden dependency changes before merge or npm publish. Use when Socket fails, a PR adds npm deps, supply-chain check, Socket alerts, /setup-socket, or “can I add this package”. Do not use for Dependabot YAML setup (dependabot skill), general npm install hardening primers (npm-security-best-practices), full DevOps strategy, or release-please wiring (release-automation).
    0
    installs
  4. ▌
    Release Automation · rhyanvargas bundle
    Wire Conventional Commits–based version and changelog automation for a repo after confirming the DevOps platform (GitHub Actions, Azure DevOps, or other). Persists the choice in project-local skill context and installs matching pipeline/config. Use when setting up release-please, auto changelog, semver tags, /setup-releases, or “automate releases”. Do not use for full DevOps strategy design, writing app feature specs, or debugging a single unrelated CI failure.
    0
    installs
  5. ▌
    Spec Driven Workflow · rhyanvargas bundle
    Draft specs, analyze requirements, plan implementation, implement from specs, review against specs (generator≠evaluator), extract specs from existing code, run surgical bugfix specs, multi-session handoff/progress, and size greenfield/brownfield work. Use when the user wants testable requirements, living specs, spec-driven development, session handoff, bugfix with regression fences, Design-First vs Requirements-First, or /draft-spec /plan-impl /implement-spec /review /extract-spec. Do not use for C4/solution architecture packets (use solution-architecture), DevOps/CI-CD strategy design, README authoring, Agent Skill optimization, AFK/Ralph automation products, or trivial one-line fixes.
    0
    installs
  6. ▌
    Solution Architecture · rhyanvargas bundle
    Design sized solution-architecture packets: outcome brief, C4 views (context, container, dynamic, deployment), ADRs, and a lite risk register. Use when the user wants an architecture diagram, C4 model, system context, container view, deployment/trust boundaries, ADR, architecture review, or /design-architecture. Do not use for feature REQ drafting (use spec-driven-workflow), CI/CD or promotion strategy (use devops-strategy-facilitator), README sync, or vendor-icon / draw.io rendering alone.
    0
    installs
  7. ▌
    Pull Request Authoring · rhyanvargas bundle
    Open or refresh GitHub pull requests with Conventional Commits titles and bodies filled from branch commits (Summary, Changes, checklist). Use when creating a PR, /create-pr, “open a pull request”, “fill the PR description”, or fixing an empty template body. Do not use for release-please/changelog wiring (release-automation), Socket triage (supply-chain-gate), code review against specs (spec-driven-workflow /review), or commit-message-only asks.
    0
    installs
  8. ▌
    Devops Strategy Facilitator · rhyanvargas bundle
    Facilitate a concise DevOps strategy session covering branching, CI/CD, environments, promotion, governance, artifacts, secrets, and rollback. Use when designing or refining delivery strategy, environment promotion, deployment governance, or when /design-devops-strategy is invoked. Do not use for wiring release-please/changelog automation (use release-automation), Socket/supply-chain PR triage (use supply-chain-gate), C4/solution architecture packets (use solution-architecture), feature specs, writing Dockerfiles or a single app pipeline, unit tests, or debugging one failed CI run.
    0
    installs