lean-vendor-substrate
Skill3 starsChanged 24 days agoApache-2.0View on GitHub
USE FOR: executing a decided vendoring of a permissively-licensed Lean 4 formalization into a project tree: verifying. DO NOT USE FOR: deciding whether to adopt or vendor a package (@lean-package-research). TRIGGERS: vendor, vendoring, vendored code, upstream formalization.
In this repository65 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-guard-judge-evalSkill
- applied-data-information-securitySkill
- applied-engineering-disciplinesSkill
- applied-legal-reasoningSkill
- epistemic-discovery-engineSkill
- epistemic-mappingSkill
- hol-metamath-adapterSkill
- isabelle-isar-adapterSkill
- itp-cross-portingSkill
- lean-ai-formalizationSkill
- lean-applied-reasoningSkill
- lean-axiom-closureSkill
- lean-bigraph-modelingSkill
- lean-bisectSkill
- lean-blueprintSkill
- lean-buildSkill
- lean-causal-reasoningSkill
- lean-competitive-mathSkill
- lean-convergence-verificationSkill
- lean-core-onlySkill
- lean-dag-visualizerSkill
- lean-deep-auditSkill
- lean-doc-feedbackSkill
- lean-doc-improvementSkill
- lean-doc-requirementsSkill
- lean-enforcementSkill
- lean-formalization-breakdownSkill
- lean-gatewaySkill
- lean-integration-protocolSkill
- lean-knowledge-formalizationSkill
- lean-math-analysisSkill
- lean-math-discreteSkill
- lean-math-dynamicalSkill
- lean-math-foundationsSkill
- lean-math-optimizationSkill
- lean-math-stochasticSkill
- lean-mweSkill
- lean-nested-learningSkill
- lean-package-researchSkill
- lean-pedagogical-expositionSkill
- lean-proof-refactorSkill
- lean-proof-repairSkill
- lean-proof-reviewSkill
- lean-proofSkill
- lean-prSkill
- lean-quality-engineSkill
- lean-replay-verificationSkill
- lean-reportSkill
- lean-researchSkill
- lean-retroactive-auditSkill
- lean-retro-methodologySkill
- lean-review-councilSkill
- lean-security-formalizationSkill
- lean-setupSkill
- lean-specificationSkill
- lean-tautology-triageSkill
- lean-upstream-portingSkill
- lean-zettelkastenSkill
- math-product-managementSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 35
STOP if the license is missing, unclear, copyleft-incompatible, or the upstream repo cannot be authenticated.
- Very specific: line 38
STOP if the port requires changes beyond import/namespace/option handling to make it compile (elaboration drift deeper than mechanical …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
lean-vendor-substrate
Vendoring is the sanctioned alternative to re-derivation when a needed theorem
Routing
- USE FOR: tasks routed to
@lean-vendor-substrate. - DO NOT USE FOR: out-of-scope tasks (delegate via
@lean-gateway).
Workflow
- Verify provenance before copying anything [discover] — record the
upstream repository, the exact commit hash, the date, and the license. Fetch
the license text into the project (e.g. a
LICENSES/<name>-<license>.txtfile) unless the upstream ships one at the vendored path. A vendoring without a pinned commit is not reviewable; refuse to proceed without one. - Check the license and the sorry-status claim [validate] — confirm the
license is permissive and compatible with the project license. If upstream
claims CI-verified
sorry-freedom, verify it locally after the port rather than trusting the claim; if the claim cannot be re-verified, downgrade to RESEARCH-MORE in@lean-package-researchterms.
Recovery & STOP
- STOP if the license is missing, unclear, copyleft-incompatible, or the
upstream repo cannot be authenticated; return to
@lean-package-researchwith the evidence. - STOP if the port requires changes beyond import/namespace/option handling to make it compile (elaboration drift deeper than mechanical rewrites); surface the drift as a decision — either document a minimal, marker-commented adaptation or park the vendoring and record the blocker.
Handoffs
- Predecessors:
@lean-package-researchfor the adoption decision and package card,@lean-researchfor the source-discovery ladder (confirm absence at the pin, find permissive-license candidates),agent:gatewayfor vendoring-focused user requests. - Successors:
@lean-enforcementto run and own the gate results,@lean-quality-enginefor milestone/package-health scoring,@lean-proof-reviewto review any corpus-authored wrapper modules built on
Detailed reference
Full encyclopedic reference, decision trees, and lookup tables live in
references/lean-vendor-substrate-handbook.md .
See also
../../references/lean-vendor-substrate-handbook.md-- Completelean-vendor-substrateHandbook../lean-gateway/SKILL.md-- Top-level skill router
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.