GitHub Universe 2026 Build once, Run on any agent A practical guide to agent skills. Andrea Griffiths Shishir Tewari Developer Experience · GitHub Data Engineering · Procore
How many times this week did you re -explain the same task to an agent? Keep it up if what you were explaining isn't written down anywhere. 2
Every pipeline had the same shape. When Every the judgment pipeline that was built from makes scratch. aSource pipeline Metriccorrect Schema lives in Backfill Pipeline Tests Deploy discovery design DDL code + PR four people’sSeven heads, steps. Same seven, every time. What was actually hard Cost of the bottleneck those four people Which grains are viable for this source are the roadmap. Four engineers held the judgment. What the metric is allowed to be called Others waited or risked inconsistency. When a join is safe, and when it fans out Shishir What mustTewari never reach Keep those four setting standards, a warehouse Senior unreviewed Manager, Data Engineering · Procore Technologies not the only people applying them. 3
SKILL DIRECTORY What is a skill? A directory the agent can discover and load. - Progressive disclosure - Name + description - Instructions after activation - Supporting files as needed 4
When I say Verifier loop proof - agent/ “skill” INPUT VERIFY VERDICT A directory the agent Original request SKILL.md PASS required canChanged discover and load. files Proof Agent Diff scripts/ via GitHub Action FAIL optional Progressive disclosure references/ PARTIAL optional Not in: worker self -assessment Name + description assets/ optional Correct the change. Verify again. Instruction body Every verdict includes file:line evidence Supporting files on demand 5
Slide 6
dataforge: fourlives The business Design Standards skills,in one file and not one of them knows anything about our data One file holds- the forge initbusiness / configcontext. boundary 1skillReads No hardcodes 2 warehouse a catalog, a table, an eight -line seed; inspects or a domain word. 3 file. + existing code; writes one writes Discovery in theover Livesdataforge.manifest.resolved.yaml manifest One execution Lives in the skillsGuidance plus declaration zones · catalogs · domains · entitiesprimitive · grains · job names · naming grammar checks Zone and catalog names How to discover a grain configures all three Domains, Grains entities, grains + grammar Every query usesWhen a join is safeLoad forge -lint forge - dbx forge - lint forge - builder from Metricexisting namingcode. grammar forge -dbx. What a good metric before namecodegen. looks like execution primitive rules as a skill orchestrator Job query, Every Mark names and job, every unsupported. deployment orderNaming, Select aSQL shape, What must not ship supported without Seven phases. Guide a human generation. one Dointerface. not guess. join safety, gates. backend. Seven checkpoints. Check execution. TheGitHub test:issue can you open -source forge the skills without a rewrite? Pull request - builder 7
8
Slide 9
One source. Three generated packages. skills/*/SKILL.md node scripts/package.mjs Plain markdown Generates all three Claude Code Cursor GitHub Copilot .claude - plugin/ .cursor - plugin/ .github/agents/ plugin.json plugin.json *.agent.md 9
Portable procedure What the host owns SKILL.md Model scripts/ Tools references/ Permissions assets/ Credentials Agent Plugins v1: plugin.json + skills/ + mcp.json 10
Skill or app? Skill fit App fit Bounded reusable Stable UI Shared state judgment. Permissions · audit Long -running control Checklist · release · migration Policy outside the model Metric pipeline 11
Three things you can do on Monday 01 Put the business Keep business names in a manifest. in one file Make every skill read it. 02 Give every skill One wrapper over the platform. one way to execute Everything else calls it. 03 Guide generation. Instructions guide. Tests and policy gates Enforce controls. can block merge or deployment. 12
Pick one task you keep explaining. What it needs → where it stops → what a reviewer sees Ask the teammate who gets interrupted. Version it. Run it in your client. Improve it. 13
Thank you Andrea Griffiths Talk repository Shishir Tewari Scan for https://github.com/githubevents/build-once-run-on-any-agent Developer Experience · GitHub Data Engineering · Procore User-supplied headshot of Andrea Griffiths User-supplied headshot of Shishir Tewari LinkedIn https://gh.io/skills26 LinkedIn https://gh.io/skills26 /in/acolombiadev/ /in/shishir-tewari-36113514/ /in/acolombiadev/ /in/shishir -tewari -36113514/
How was this session? We do actually read these. It's how Universe gets better every year. Scan to review.