Super industry ops
Portable Markdown skill for AI vibe coding with industry operations: logistics, manufacturing, procurement, production scheduling, supply chain, and operational quality.
npx -y skills add arpitexplores/super-industry-opsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Industry-specific operations: logistics, manufacturing, procurement, and quality workflows.
SKILL.md
1.6 KB, 318 tokens by cl100k_base, as published. Nobody here has run it
Super Industry Operations
Overview
Apply domain-specific operational guidance with clear processes and metrics.
User Intent Examples
- "Need help with Energy Procurement for my product/site."
- "Create a plan for Logistics Exception Management."
- "Audit or improve Production Scheduling."
Workflow
- Define operational scope and KPIs.
- Assess current process and constraints.
- Design improved workflow and controls.
- Evaluate cost, risk, and compliance impacts.
- Deliver implementation steps and monitoring.
Minimal Intake Questions
- Primary goal or outcome
- Scope (pages, systems, teams, or timeframe)
- Constraints (tools, budget, timeline)
Output Format
- Process map and KPI plan
- Operational improvements list
- Risk and compliance notes
- Implementation checklist
Routing Map (Modules)
- Energy Procurement ->
references/modules/energy-procurement.md - Logistics Exception Management ->
references/modules/logistics-exception-management.md - Production Scheduling ->
references/modules/production-scheduling.md
Bundled References
references/modules/scripts/assets/agents/
Compatibility Notes
- If any module references slash commands or tool-specific paths, translate them into plain-language steps.
- Keep outputs platform-agnostic unless the user specifies a specific tool, stack, or agent.
Guardrails
- Do not assume regulatory context.
- Separate strategic vs tactical changes.
- Make KPIs measurable and time-bound.
Gives 0 of the 12 instructions most ship operate skills give in 318 tokens
Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-06
- document a rollback plan before deploymentin 40 of 779, across 21 files
- create an annotated git tagin 21 of 779, across 20 files
- Run the test suitein 20 of 779
- update the changelogin 20 of 779, across 18 files
- verify deployment health after launchin 19 of 779, across 10 files
- clean up feature flags after full rolloutin 18 of 779, across 10 files
- verify the working tree is cleanin 18 of 779
- test both feature flag statesin 17 of 779, across 9 files
- Make database migrations backward-compatiblein 16 of 779, across 8 files
- set up error monitoring before launchin 15 of 779, across 7 files
- monitor metrics at each rollout stagein 14 of 779, across 5 files
- create a github releasein 14 of 779
Said here and by no other author read
- define operational scope and KPIs
- assess current process and constraints
- design improved workflow and controls
- evaluate cost risk and compliance impacts
- deliver implementation steps and monitoring
- translate tool-specific paths into plain language
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.