Pymc Bayesian Modeling

foryourhealth111-pixel/pymc-bayesian-modeling

Compatibility alias for the descriptive PyMC skill name. Delegate to the canonical local `pymc` payload while preserving route and README compatibility.

277 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

2583

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/foryourhealth111-pixel/Vibe-Skills --skill pymc-bayesian-modeling

The instruction itself

4 sections, as written by the author

pymc-bayesian-modeling (Compatibility Alias)

Purpose

Provide a stable descriptive alias for Bayesian modeling workflows that are

canonically maintained under the sibling pymc skill directory.

This preserves:

README-facing descriptive naming
existing skills-lock and catalog entries
route compatibility for callers that still ask for pymc-bayesian-modeling

Resolution Order

Use the canonical local pymc skill payload first.
Reuse its assets, references, and scripts:
../pymc/SKILL.md
../pymc/assets/**
../pymc/references/**
../pymc/scripts/**
Keep this alias thin and free of its own duplicated heavy payload.

Minimal Workflow

Read ../pymc/SKILL.md for the full PyMC workflow.
Use the canonical templates and diagnostic scripts from ../pymc/.
Report results under the requested alias name only for user-facing continuity.

How to use it

Copy the folder

Take foryourhealth111-pixel/pymc-bayesian-modeling from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.