manufacturing-expert▌
personamanagmentlayer/pcl · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Expert guidance for manufacturing systems, Industry 4.0, production optimization, quality control, and smart factory implementations.
Manufacturing Expert
Expert guidance for manufacturing systems, Industry 4.0, production optimization, quality control, and smart factory implementations.
Core Concepts
Manufacturing Systems
- Manufacturing Execution Systems (MES)
- Enterprise Resource Planning (ERP)
- Computer-Aided Manufacturing (CAM)
- Programmable Logic Controllers (PLC)
- Industrial Internet of Things (IIoT)
- Supply Chain Management (SCM)
- Warehouse Management Systems (WMS)
Industry 4.0
- Smart factories
- Digital twins
- Predictive maintenance
- Autonomous robotics
- Augmented reality for operations
- Edge computing
- Cyber-physical systems
Standards and Protocols
- OPC UA (Open Platform Communications)
- ISA-95 (Enterprise-Control System Integration)
- MTConnect (manufacturing data exchange)
- MQTT for IIoT
- EtherCAT (real-time Ethernet)
- PROFINET
- ISO 9001 (Quality Management)
Manufacturing Execution System (MES)
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() - machinHow to use manufacturing-expert on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add manufacturing-expert
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches manufacturing-expert from GitHub repository personamanagmentlayer/pcl and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate manufacturing-expert. Access the skill through slash commands (e.g., /manufacturing-expert) or your agent's skill management interface.
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ 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.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★29 reviews- ★★★★★Shikha Mishra· Dec 8, 2024
Useful defaults in manufacturing-expert — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Sakura Flores· Dec 4, 2024
manufacturing-expert fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Rahul Santra· Nov 27, 2024
manufacturing-expert is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Kiara Smith· Nov 23, 2024
Registry listing for manufacturing-expert matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Hana Chen· Nov 7, 2024
Solid pick for teams standardizing on skills: manufacturing-expert is focused, and the summary matches what you get after install.
- ★★★★★William Reddy· Oct 26, 2024
manufacturing-expert has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Pratham Ware· Oct 18, 2024
Keeps context tight: manufacturing-expert is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Kiara Jain· Oct 14, 2024
manufacturing-expert reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Camila Garcia· Sep 9, 2024
Useful defaults in manufacturing-expert — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Aanya Smith· Sep 5, 2024
I recommend manufacturing-expert for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 29