coming soon
The Pip Skill Market
Skills developed by mining experts, for every department from exploration to production. Experts upload what they know; geologists, engineers and planners download what they need. Every skill you add unlocks a new job Pip can do for you, by voice.
so what's a skill?
A design method, packed so Pip can use it
A skill is everything Pip needs to do one engineering job the way an expert does it. Pip's stope drill design is the first one, and it's built like this:
- Rules with units, sensible ranges and what each one means, so planners can change them by voice.
- A generator that turns the rules and your CAD into a design.
- Checks on every result: collisions, coverage, and anything the author cares about.
- Worked examples that must keep passing whenever the skill changes.
- A version, a change log and a backlog of what planners have asked it to do next.
- Commands: a skill can use any command your design software's connector offers, and Pip still asks before anything changes.
inside: stope drill design
| Rule | Default |
|---|---|
| Hole diameter | 89 mm |
| Burden | 2.0 m |
| Toe spacing | 2.2 m |
| Fan pivot | 2 m above the drive floor |
| Boxhole | 760 mm |
| Rise | 3 × 3 m |
| Brow cables | 6.1 m, between firings |
"Stope 10 with 2.5 m burden" changes one rule for one design. "Make that my default" saves it.
new · skills that sync themselves
Keep your skills in GitHub. Pip keeps up.
Point Pip at your team's skills repository and it takes new versions on its own, every half hour or when you say "sync the skills".
- Pip's own changes (skill updates you approved, saved design defaults, the request backlog) stay as local commits on your PC and are never pushed.
- When GitHub changed the same lines, Pip keeps its version and lists the files to merge by hand, instead of overwriting anything.
- A read-only key for the repository means planners don't need a GitHub account of their own.
- Attach a skill to any request: pick it from the list, or type
/namebefore your question.
Illustrative names and versions.
two ways in
Upload what you know. Download what you need.
Upload a skill
Package your method
Your rules with units and ranges, the generator that draws the design, and the checks you'd do by hand.
Prove it
Your worked examples and Pip's read-only checks run before anything is published.
Publish and keep it sharp
Under your name, with a version and change log. Planners' requests come back to you as a backlog.
Download a skill
Browse
Find a skill for the job. See who made it, what it checks and how it has changed.
Add it to Pip
Pip loads it on your PC, next to your data and models. Nothing about your mine goes to the author.
Ask
"Design the ground support for this drive." Anything that writes into CAD or the schedule still waits for your yes.
on the shelf, one day
Skills we'd love to see
One skill ships today and three are in testing, all from underground planning. The rest are concepts from across the mine: examples of what experts could publish. Got one of these in your head already?
house rules
Every skill plays by Pip's rules
Read-only until you say yes
A skill can read the schedule and CAD and draft a design. Writing anything still takes your two taps, and Pip reads it back.
Checked before it ships
Each new version has to pass its own worked examples and Pip's checks before anyone can download it.
Versions you can trust
Every skill has a version and a change log, so you know which rules made a design. A bad update can be rolled back.
Private when it should be
Your company's standards can be a skill only your team sees. Your schedule never goes to a skill's author.
Planners shape it
Ask for something a skill can't do yet and Pip adds it to that skill's backlog, for the author to pick up.
Runs on your PC
Skills run in the Pip server beside your design software, with your data, under your own Claude sign-in.
Pip is digging the shelves out now
Want in early?
If you're a mining engineer with a method worth sharing, or a planner who wants first pick, drop us a line.