A Claude Code skill that automatically converts Laserfiche workflow files (.wfi / .xml) into polished, professional HTML documentation with two audience-targeted views:
- End-User Guide -- plain-language explanation of what the workflow does, when it runs, and what to expect
- Technical Reference -- full admin-level breakdown with activity maps, token inventories, field references, and configuration details
- Parses Laserfiche Workflow Designer exports (
.wfiand.xml) - Recursively maps all activities, branches, conditions, and loops
- Translates internal class names into human-readable activity descriptions
- Generates a single standalone HTML file with:
- Fixed navigation bar and sidebar
- Color-coded sections (green for users, blue for admins)
- Professional typography (DM Sans + JetBrains Mono)
- At-a-glance summary card
- Activity tree visualization with icons
- Token and field inventory tables
- Identifies disabled activities and exception paths
- Handles sub-workflow references, complex token expressions, and unknown activity types gracefully
- Claude Code CLI installed, or access to Claude.ai with the Projects feature
- A Laserfiche workflow file (
.wfior.xml) exported from Workflow Designer
-
Clone this repository:
git clone https://github.com/YOUR_USERNAME/lfdocbuilder.git
-
Install the skill:
claude install skill/laserfiche-workflow-doc.skill
This registers the skill so Claude Code can use it automatically when you reference a workflow file.
-
Use it: Open Claude Code in any directory containing a
.wfifile and ask Claude to document it (see Sample Prompts below).
-
Download the skill file from this repository:
skill/laserfiche-workflow-doc.skill -
Create a new Project on claude.ai:
- Click Projects in the sidebar
- Click Create Project
- Give it a name like "Laserfiche Workflow Docs"
-
Add the skill to your project:
- In your project, go to Project Knowledge
- Upload the
laserfiche-workflow-doc.skillfile
-
Use it: Start a new conversation within that project, upload your
.wfifile, and ask Claude to document it.
If you prefer not to use claude install, you can add the skill manually:
-
Copy the
skill/laserfiche-workflow-doc.skillfile to your Claude Code skills directory:- macOS/Linux:
~/.claude/skills/ - Windows:
%USERPROFILE%\.claude\skills\
- macOS/Linux:
-
Restart Claude Code to pick up the new skill.
Once the skill is installed, you can use natural language to trigger it. Here are some examples:
Document this workflow
Upload or reference a
.wfifile in the same directory.
Analyze ASSR_CreateNewParcel.wfi and generate documentation
What does this workflow do?
Create documentation for this Laserfiche workflow.
I need to share it with non-technical staff in our assessor's office.
Generate a technical reference for this workflow --
I need to understand the branching logic and token flow before editing it.
Document this LF workflow. Focus on the error handling paths
so I can troubleshoot why documents end up in the exceptions folder.
I have three workflow files in this folder.
Document each one and highlight any shared tokens or field dependencies.
I just inherited this workflow from the previous admin.
Can you explain what it does and flag anything that looks misconfigured?
Our assessor's office needs to train new staff on this process.
Create a user-friendly guide from this workflow file.
lfdocbuilder/
├── skill/
│ └── laserfiche-workflow-doc.skill # Claude Code skill (ZIP archive)
│ ├── SKILL.md # Main skill instructions
│ └── references/
│ ├── activity-types.md # Activity class name mappings
│ └── html-template.md # CSS design system & HTML patterns
├── examples/
│ └── ASSR_CreateNewParcel.wfi # Sample workflow file for testing
└── README.md
| File | Purpose |
|---|---|
SKILL.md |
Core instructions -- tells Claude how to parse workflow XML, what to extract, and how to structure the two documentation views |
references/activity-types.md |
Maps Laserfiche activity class names (e.g., ForEachEntryActivityProxy) to human-readable names and behavior descriptions |
references/html-template.md |
Complete CSS design system with color palette, typography, layout components, callout boxes, and activity tree styling |
The skill generates a single standalone HTML file containing:
| Section | Audience | Color Accent |
|---|---|---|
| Workflow At-a-Glance | Everyone | Neutral |
| End-User Guide | Staff / non-technical | Green |
| Technical Reference | Admins / developers | Blue |
The HTML is fully self-contained with inline CSS and only depends on Google Fonts CDN for typography.
The skill recognizes and documents these Laserfiche activity categories:
- Control Flow -- If/Else branching, For Each loops, Parallel execution, Sequences
- Repository Operations -- Search, Move, Rename, Delete, Create Folder
- Metadata Operations -- Assign Template, Set Fields, Retrieve Field Values, Remove Template
- Token/Variable Operations -- Create Token, Parse Text, Format Token, Calculate Value
- Communication -- Send Email
- Process Control -- Start Sub-Workflow, Wait for Event, Delay, Terminate
- User Interaction -- User Task, Assign User Task
Unknown activity types are interpreted from the XML and flagged in the output.
The examples/ directory includes ASSR_CreateNewParcel.wfi, a real-world assessor's office workflow that creates new parcel records. Use it to test the skill:
Analyze examples/ASSR_CreateNewParcel.wfi and generate documentation
Contributions are welcome! If you work with Laserfiche and encounter activity types or workflow patterns that aren't handled well, please open an issue with:
- A description of the activity type or pattern
- A sanitized XML snippet if possible
- What the expected documentation output should look like
MIT License. See LICENSE for details.