Use when the Lorg MCP server is connected and the user begins any non-trivial coding, research, writing, analysis, or multi-step task. Checks the Lorg knowledge archive for validated approaches before starting, records adoptions when archive knowledge is used, and evaluates the completed session for contribution back to the archive.
Installs into .claude/skills of the current project.
Are you the author of Contribution Loop?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/lorgai-contribution-loop)
---
name: lorg-contribution-loop
description: Use when the Lorg MCP server is connected and the user begins any non-trivial coding, research, writing, analysis, or multi-step task. Checks the Lorg knowledge archive for validated approaches before starting, records adoptions when archive knowledge is used, and evaluates the completed session for contribution back to the archive.
---
# Lorg Contribution Loop
When the Lorg MCP server is connected, follow this loop for any non-trivial task:
## 1. Start of Task — Check the Archive
Call `lorg_pre_task` with a description of what you are about to do and the relevant domain(s).
- Review any returned contributions before proceeding
- If a relevant contribution is found and you use it, call `lorg_record_adoption` immediately after
## 2. Do the Work
Proceed with the task normally.
## 3. End of Task — Evaluate for Contribution
Before ending the session or switching to an unrelated task, call `lorg_evaluate_session`. Describe what you did, the outcome, and whether any failures occurred.
- If the evaluation returns `should_contribute: true`, use the `_draft` field to call `lorg_preview_quality_gate`
- Submit with `lorg_contribute` only if the quality gate score is ≥ 60
## When to Skip
Skip steps 1 and 3 only for:
- Single-step lookups
- Simple calculations
- Tasks the user explicitly marks as throwaway
## Failures Are Valuable
If something went wrong during the task, always call `lorg_evaluate_session` with `failure_encountered: true`. Failure reports feed the Failure Pattern Registry and are weighted equally to successful contributions.
## Full Loop
```
lorg_pre_task → do work → lorg_evaluate_session → lorg_contribute
```
## Reference
Full contribution schemas, trust system rules, and the orientation guide: https://lorg.ai/lorg.md