Anthropic style "Moqui Skill"

Technical Discussion
1

Have you heard about Anthropic’s new “skills” standard? It’s basically a bundle of prompts, scripts and reference that can plug in to your interactive coding agent and give it a leg up on a particular topic. You can get more details here: Claude Skills: Customize AI for your workflows \ Anthropic

I had already been working on a set of materials designed to do something similar but just as documents that I would load into the context. This goes a little further because the coding agent has specific support for the structures in a “skill”. Luckily, Anthropic has a skill for making skills so I put that to work: skills/skill-creator at main · anthropics/skills · GitHub

I’ve been using Opencode with GLM-4.6 lately because it is 10x cheaper than Anthropic Claude and, from my perspective anyway, quite competitive. I’ve been a fan of GLM since I stumbled across it in connection to Tsinghua University’s video synthesis efforts. It’s been interesting to watch it gain traction so rapidly since then. Opencode is 100% Open Source. The original authors spun out to create Crush, a similar product under a more restrictive license. Other Opencode contributors, however, kept the party going and now it is growing rapidly. I found an announcement about a plug-in implementing Anthropic Skills so I tried it out and quickly found myself wanting something for Moqui.

So I used the skill creating skill to create a Moqui skill. I’ve been coding with it all day and it hasn’t blown up. I think it’s making things better? It seems like it is. I’d be curious to hear back from anyone who tries it:

2

Thanks Ean! The reference documents are in itself a valuable asset. Where did you get them from?

3

I generated them with AI as described above. :smiley:

4

Ah, I see. Well it might be good to proofread them before then. I saw for example the transaction="timeout" attribute on the service, but there is no timeout value between the transaction options. There is however a transaction-timeout attribute that specifies the timeout amount in seconds.

5

Thank you for catching that transaction attribute issue! You were absolutely right about
transaction=“timeout” being invalid. I’ve now updated the moqui-skill to address this and align with upstream Moqui framework practices.

:white_check_mark: Fixed Issues

Invalid Attribute: Changed transaction=“timeout” → proper usage:

• Standard services: No transaction attribute (framework default)
• Critical operations: transaction=“force-new” with appropriate timeout
• Removed: transaction-timeout=“60” (too short - framework uses 600-3600s)

:bar_chart: Framework Analysis Results

I analyzed 3,230+ Moqui framework service definitions to understand upstream patterns:

• 98.5% use framework default (no transaction attribute)
• 1.5% use explicit attributes:
• transaction=“force-new” (63%) - financial/bulk operations
• transaction=“cache” (22%) - being removed due to locking issues
• transaction=“ignore” (8%) - maintenance tasks

Updated Files

  1. SKILL.md - Added comprehensive transaction management guidance
  2. scripts/generate_service.py - Now uses framework defaults
  3. references/service_patterns.md - Updated examples with proper patterns

Key Guidance Added

• Default: No transaction attribute (let framework handle it)
• Critical: Use transaction=“force-new” for financial/bulk operations
• Timeout: Only add for operations >5 minutes (600-3600s range)
• Avoid: transaction=“cache” (causes locking issues in framework)

The skill now mirrors actual Moqui framework practices and provides clear guidance on when to deviate from defaults. Thanks again for the feedback - this significantly improves the quality and accuracy of the skill!

Commit: 173c8b6 - Changes are ready for review.

6

Similar but different, Langfuse offers an MCP of their own docs: Langfuse Docs MCP Server - Langfuse