Expert guidance for manufacturing systems, Industry 4.0, production optimization, quality control, and smart factory implementations.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmanufacturing-expertExecute the skills CLI command in your project's root directory to begin installation:
Fetches manufacturing-expert from personamanagmentlayer/pcl and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate manufacturing-expert. Access via /manufacturing-expert in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
15
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
15
stars
Expert guidance for manufacturing systems, Industry 4.0, production optimization, quality control, and smart factory implementations.
from dataclasses import dataclass
from datetime import datetime, timedelta
from typing import List, Optional
from enum import Enum
class OrderStatus(Enum):
PENDING = "pending"
IN_PROGRESS = "in_progress"
COMPLETED = "completed"
ON_HOLD = "on_hold"
CANCELLED = "cancelled"
class MachineStatus(Enum):
IDLE = "idle"
RUNNING = "running"
MAINTENANCE = "maintenance"
ERROR = "error"
OFFLINE = "offline"
@dataclass
class WorkOrder:
"""Manufacturing work order"""
order_id: str
product_id: str
quantity: int
priority: int # 1 (highest) to 5 (lowest)
due_date: datetime
status: OrderStatus
assigned_line: Optional[str]
started_at: Optional[datetime]
completed_at: Optional[datetime]
actual_quantity: int = 0
defect_quantity: int = 0
@dataclass
class Machine:
"""Production machine/equipment"""
machine_id: str
machine_type: str
status: MachineStatus
current_order: Optional[str]
production_rate: float # units per hour
uptime_percentage: float
last_maintenance: datetime
next_maintenance: datetime
oee: float # Overall Equipment Effectiveness
@dataclass
class ProductionMetrics:
"""Real-time production metrics"""
timestamp: datetime
line_id: str
produced_units: int
defective_units: int
downtime_minutes: int
cycle_time_seconds: float
efficiency_percentage: float
class ManufacturingExecutionSystem:
"""MES for production management"""
def __init__(self):
self.work_orders = {}
self.machines = {}
self.production_data = []
def create_work_order(self,
product_id: str,
quantity: int,
due_date: datetime,
priority: int = 3) -> WorkOrder:
"""Create new production work order"""
order_id = self._generate_order_id()
order = WorkOrder(
order_id=order_id,
product_id=product_id,
quantity=quantity,
priority=priority,
due_date=due_date,
status=OrderStatus.PENDING,
assigned_line=None,
started_at=None,
completed_at=None
)
self.work_orders[order_id] = order
return order
def schedule_production(self) -> List[dict]:
"""Schedule work orders to production lines"""
# Get pending orders sorted by priority and due date
pending_orders = [
order for order in self.work_orders.values()
if order.status == OrderStatus.PENDING
]
sorted_orders = sorted(
pending_orders,
key=lambda x: (x.priority, x.due_date)
)
# Get available machines
available_machines = [
machine for machine in self.machines.values()
if machine.status in [MachineStatus.IDLE, MachineStatus.RUNNING]
]
schedule = []
for order in sorted_orders:
# Find best machine for this order
best_machine = self._find_best_machine(order, available_machines)
if best_machine:
# Calculate estimated completion time
production_time = order.quantity / best_machine.production_rate
estimated_completion = datetime.now() + timedelta(hours=production_time)
schedule.append({
'order_id': order.order_id,
'machine_id': best_machine.machine_id,
'estimated_start': datetime.now(),
'estimated_completion': estimated_completion,
'estimated_duration_hours': production_time
})
# Update order
order.assigned_line = best_machine.machine_id
order.status = OrderStatus.IN_PROGRESS
return schedule
def _find_best_machine(self, order: WorkOrder, machines: List[Machine]) -> Optional[Machine]:
"""Find optimal machine for work order"""
if not machines:
return None
# Score machines based on multiple factors
scored_machines = []
for machine in machines:
score = 0
# Prefer machines with higher OEE
score += machine.oee * 50
# Prefer machines that are idle
if machine.status == MachineStatus.IDLE:
score += 30
# Prefer machines with recent maintenance
days_since_maintenance = (datetime.now() - machinMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
erichowens/some_claude_skills
sickn33/antigravity-awesome-skills
erichowens/some_claude_skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
Useful defaults in manufacturing-expert — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
manufacturing-expert fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
manufacturing-expert is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for manufacturing-expert matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: manufacturing-expert is focused, and the summary matches what you get after install.
manufacturing-expert has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: manufacturing-expert is the kind of skill you can hand to a new teammate without a long onboarding doc.
manufacturing-expert reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in manufacturing-expert — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend manufacturing-expert for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 29