DSH Market
V

Vibe Skills

by foryourhealth111-pixel · foryourhealth111-pixel/Vibe-Skills

InstallableSkillcopy into placefresh

VibeSkills is a general-purpose Skill that automatically routes local Skills and intelligently orchestrates harness workflows.

Install Vibe Skills

Not a bundle: drop the SKILL.md directory into one of the skill roots DSH scans. No `dsh plugin add`, no build step.

This is a skill, not a bundle. Skills are not installed with dsh plugin add — a skill is a directory containing SKILL.md that DSH discovers by scanning its skill roots. Clone it into one of those roots and it is available on the next session.

Clone into your user skill root ($DSH_HOME/skills)

mkdir -p ~/.dsh/skills
git clone https://github.com/foryourhealth111-pixel/Vibe-Skills.git ~/.dsh/skills/Vibe-Skills
RankRootPath
100project-dsh<project>/.dsh/skills
200project-agents<project>/.agents/skills
300customcustomSkillDirs in your config
400user-dsh$DSH_HOME/skills (default ~/.dsh/skills)
500user-agents$DSH_AGENTS_HOME/skills (default ~/.agents/skills)

Lower rank wins when two roots hold a skill with the same name. Put it in a project root instead of the user root when it should only apply to one repository.

Prerequisites

API key
Not required.
Network access
Required at runtime.
Language
Python

Install check

Every field the verdict was derived from, so you can re-derive it yourself

Field checkedResultWeightWhat the spec says about it
lifecycleScriptspassinfono install-time scripts
entityTypepassinfoskill is not installed via `dsh plugin add`
Verdict reason
skill uses its own install path, so bundle checks do not apply
package.json read
bundled/skills/digital-brain/package.json
Rules applied from
docs/user/develop/basic/publish.md
Checked at
2026-08-15

From the README

Excerpt as published by the author, plain text, unedited

> **Task** > > *Use public data to complete a reproducible classification experiment and deliver a data audit, statistical review, 4 result figures, a scientific report, and a 7-slide group-meeting deck.* The diagram shows what happened after the requirement and plan were approved: how the task was executed, what it produced, and how the result was checked. The task used the `L` workflow and proceeded in order. During publication preparation, the configured folders on the same host contained more than 100 Skills. VibeSkills reviewed the candidates and their `SKILL.md` files, selected 7 for this task, and arranged the work into 5 groups and 10 work units. Those units covered environment setup, data audit, modeling, statistical review, figures, the report, and the slide deck. After the work

Topics

GitHub topics on this repository

Related entries

Nearest entries by similarity — this one landed in no themed cluster