2.6k
GitHub Stars
4
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill erp-integration-analysis- _meta.json494 B
- claw.json493 B
- instructions.md1.2 KB
- SKILL.md24.5 KB
Overview
This skill analyzes ERP system integration for construction data flows and maps interactions between ERP modules and external systems. It identifies critical flows, bottlenecks, and provides actionable recommendations to optimize data movement and reliability. The analysis produces a numeric integration score, a set of prioritized recommendations, and a data-flow diagram for planning work.
How this skill works
The analyzer inspects ERP module dependencies, declared integration points, and optional transaction logs to map internal and external data flows. It classifies flows by data type, frequency, method (API, ETL, file export, etc.), direction, volume, and criticality, then calculates an integration score and detects bottlenecks. The output includes enhanced flow details, error and volume indicators from logs, and concrete recommendations to reduce manual and file-based bottlenecks.
When to use it
- During ERP selection or upgrade planning for construction firms
- When auditing existing ERP integrations to improve reliability
- Before automating manual handoffs between modules
- To prioritize integration work after merger or system consolidation
- When monitoring integration health using transaction logs
Best practices
- Inventory all modules and external systems before running analysis
- Include transaction logs to surface error rates and real-world volumes
- Prioritize automating manual and file-export flows first
- Favor API/webhook/message-queue methods for critical, high-volume flows
- Use the integration score and bottleneck list to plan phased remediation
Example use cases
- Map finance, cost control, procurement and inventory flows to prevent duplicate transactions
- Detect high-error flows from subcontracting to billing and prioritize fixes
- Recommend migrating daily ETL or file exports to APIs for near-real-time costing
- Assess integration readiness and gaps before deploying a new project-management module
- Generate a remediation roadmap with quick wins (automate manual exports, improve low-reliability endpoints)
FAQ
Provide an ERPSystem definition, integration points, list of external systems, and optional transaction logs for richer analysis.
How is the integration score calculated?
The score averages factors: API availability, integration method quality, coverage of predefined critical flows, and flow health derived from issues and logs.
Can it recommend specific integration technologies?
Yes. Recommendations prioritize APIs/webhooks/message queues for critical flows and suggest ETL or file exports only where appropriate.