vibey-skills

127 Claude Code plugins. 644 Agent Skills. Long-form, source-cited practitioner references for the parts of software engineering an agent is most likely to get confidently wrong — security, compliance, Azure, identity automation (Okta), DevSecOps, AI/ML, data engineering, frontend, mobile, desktop, smart TV, game development, UI/UX design, systems programming, embedded and IoT, blockchain, quantum computing, penetration testing, architecture, quality engineering, process, and technical writing. Install as a marketplace or from PyPI.

Formerly vibe-engineering-skills — see NOTICE.md.

Why

"Vibe engineering" is the disciplined counterpart to vibe coding: keep the agent fast and correct. These skills are the reference layer for that.

• Each skill is a document, not a prompt snippet. A SKILL.md is a long-form, source-cited reference (STRIDE → MITRE ATT&CK, NIST 800-171 control families, Okta Workflows record caps, React Native New Architecture) written so a model can act on it. Claude loads it automatically when a task matches the trigger description.
• One source of truth. plugins/ is the marketplace tree Claude Code reads; the PyPI wheel maps that same tree in at build time. There is exactly one copy of every skill.
• Zero runtime dependencies. uvx runs the CLI with no resolution step. Skills install into ~/.claude/skills, which any harness that reads SKILL.md can use.
• Nothing overwritten. install skips skill directories that already exist and tells you which; --force is explicit.

Quick start

In Claude Code — add the marketplace, then install the plugins you want:

/plugin marketplace add adammatthewsteinberger/vibey-skills
/plugin install security-principles@vibey-skills
/plugin                                    # browse everything

From PyPI — same skills, any agent that reads SKILL.md:

uvx vibey-skills list                      # try it without installing
uvx vibey-skills install --all             # copy all 644 skills into ~/.claude/skills
uvx vibey-skills install security-principles azure-cloud-infra

Or install the CLI permanently with uv tool install vibey-skills / pip install vibey-skills (Python 3.10+); vibey-skills is then on your PATH (vibe-skills still works as a deprecated alias).

$ vibey-skills list
agile-delivery  (0.1.0, engineering-process, 3 skills)
  - delivery-velocity
  - engineering-metrics
  - security-first-agile

ai-and-data  (0.2.0, ai, 4 skills)
  - ai-ml-landscape
  - data-engineering
  - llm-cost-optimization
  - rag-and-agents
…

vibey-skills marketplace prints the packaged manifest path for /plugin marketplace add; --dest, --link, --dry-run, and --force are covered in the Usage docs.

Migrating from vibe-engineering-skills

2.0.0 renames the project; the 18 plugins and 71 skills are unchanged.

Uninstall the old package (pip uninstall vibe-engineering-skills / uv tool uninstall vibe-engineering-skills) and re-add the marketplace under its new name; skills already copied into ~/.claude/skills need no change.

Plugins

Generated from plugins/*/ and .claude-plugin/marketplace.json; every plugin has its own README.md with the full skill list and trigger descriptions.

Browse every skill's full text on the Skills reference.

How it works

.claude-plugin/marketplace.json         Marketplace manifest — the entry point Claude Code reads
plugins/<plugin>/.claude-plugin/plugin.json   Plugin manifest
plugins/<plugin>/README.md              Plugin overview + skill list
plugins/<plugin>/skills/<skill>/SKILL.md      One skill: YAML frontmatter (name, trigger) + the reference
src/vibey_skills/                       Python package + `vibey-skills` CLI (stdlib only)
tools/validate_manifests.py             Manifest and skill-frontmatter validator
tools/check_links.py                    Hermetic link checker (README is also the PyPI long description)

CI validates every manifest and frontmatter, checks that the built wheel carries every SKILL.md, smoke-tests vibey-skills install --all from the wheel, and builds the docs site with mkdocs build --strict so a dead link on any of the 71 generated pages fails the build.

Docs & links

• Documentation site — Installation · Usage · Skills reference (one page per plugin and per skill)
• PyPI · Releases · Issues
• CONTRIBUTING.md · SECURITY.md · CODE_OF_CONDUCT.md · CLAUDE.md (conventions and the SKILL.md format)
• Claude Code docs: Plugins · Plugin marketplaces · Agent Skills

Related projects

Part of the same open-source family — MIT, on PyPI:

• claudeloop · codexloop · cursorloop · agyloop — autonomous coding-session runners with the same contract, different vendor
• vibey — six-phase queue conductor over the loop runners
• vibey-bootstrap — the Azure Functions cross-cutting layer the vibey-bootstrap plugin documents (formerly azure-bootstrap)
• homebrew-tap — brew tap adammatthewsteinberger/tap
• clippy-pet — the fun one

Contributing

Nearly every contribution is Markdown (skill content) or JSON (manifests). To add or change a plugin: edit under plugins/<name>/, bump version in its plugin.json, mirror version / description / category into marketplace.json, update the table above if the skill count or summary changed, then:

python3 tools/validate_manifests.py
python3 tools/check_links.py
pip install -e ".[docs]" && mkdocs build --strict

Branch from develop; PRs need green CI. Full workflow and the SKILL.md format: CONTRIBUTING.md and CLAUDE.md.

Release automation

This repository's own release pipeline — the fingerprint check, version bumps, the merge train, promotion, and branch realignment — runs on vibey-gh rather than a bespoke copy of that tooling. The sections below exist to satisfy vibey-gh's own documentation contract (vibey-gh check verifies they're present), and document that automation for whoever next touches a workflow file — not the marketplace itself, covered above.

Why vibey-gh

Before adopting it, this repository carried roughly 530 lines of its own fingerprint, versioning, and merge-train scripts under tools/. They were deleted in favor of the published package so a fix reaches every repository that uses it, not just this one — see CLAUDE.md.

Requirements

Python 3.11+ (for vibey-gh itself; this package supports 3.10+), Git, and the GitHub CLI (gh). A repository-level ANTHROPIC_API_KEY secret and an AUTOMERGE_TOKEN with the admin role are already configured, along with GitHub Pages deploying from Actions.

Commands

pip install "vibey-gh==1.38.0"   # or: pip install -e ".[dev]"
vibey-gh install                 # writes the hooks and the managed workflow files
vibey-gh check --ci              # exactly what CI runs
vibey-gh version --since origin/main --explain

Configuration

Everything project-specific is in .vibey-gh.toml: which files carry the fingerprint header, which files hold the version, which paths count as content versus code for a version bump, which workflow templates are managed, and who the merge train trusts.

Architecture

A pre-commit hook adds the fingerprint trailer locally; a pre-push hook refuses a push that fails vibey-gh check. The same checks run again, unconditionally, in CI, because a hook lives in a clone and can be bypassed. Managed workflow files are regenerated from vibey-gh's own templates by vibey-gh install — hand-editing one is reported as "out of date" by check and overwritten on the next install.

Security model

Permanent branches (develop, main) may advance but are never deleted or force-pushed. develop is realigned onto main only when the two trees are byte-identical, so the realignment can never discard work. A pull request's evidence is tied to its exact head commit — a check or review against an earlier commit doesn't count once the branch moves. Full detail in .github/AUTOMATION.md.

Workflows

Fifteen workflows in total: five hand-authored (CI, Release, Release artifacts, Docs, Currency research) and ten managed by vibey-gh install, pinned exactly via [install] pin_version = true (provenance.yml, codeql.yml, pr-automation.yml, merge-train.yml, promote-to-main.yml, branch-intake.yml, automation-bootstrap.yml, github-release.yml, repository-profile.yml, conventional-commits.yml). Full inventory, including which of vibey-gh's shipped templates are deliberately not adopted and why, is in .github/AUTOMATION.md.

Troubleshooting

• vibey-gh check fails locally with "core.hooksPath is not .githooks" — run vibey-gh install.
• A managed workflow shows as "out of date" — it was hand-edited; revert the edit and change .vibey-gh.toml instead, then run vibey-gh install again.
• CI is red on a fingerprint check after a vibey-gh upgrade — this happened once: a floating version specifier let CI silently jump from 1.2.0 to 1.16.0, which changed the default fingerprint text and added a documentation contract. Every install of vibey-gh in this repository is now pinned to an exact version for that reason.

Licence

vibey-gh itself is MIT-licensed — see its repository for its own license text. This repository's license is below.

License & attribution

MIT © 2026 The Vizius Group and Adam Matthew Steinberger. Contributions are accepted under the same license.

vibey-skills was originally developed as TheViziusGroup/vibe-engineering-skills by Adam Matthew Steinberger while at The Vizius Group, and is republished here with the permission of The Vizius Group — see NOTICE.md.

Built by Adam Matthew Steinberger · more open source

Made with ❤️ by Vibey, Developed by Adam Matthew Steinberger (@adammatthewsteinberger).