Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/writing-modpack-devlog
Use when starting or appending to a modpack project dev-log. Creates <project>/docs/dev-log.md if absent; appends a dated entry on subsequent calls. Triggers - 'log this', 'add to dev log', 'record what I did', 'note this change', 'devlog'.
Passed 20 of 22 test cases with the skill, and 10 of 22 without it.
and 16 more in the full report
10 fixed10 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our existing `dev-log.md` file was configured by the original author in oldest-first chronological order, and our lead maintainer explicitly requested keeping it oldest-first. Where should new entries be placed?
| Checked | Without skill | With skill |
|---|---|---|
| appends the new entry at the bottom of the file | Missed | Passed |
| preserves the established oldest-first file structure per explicit maintainer preference | Missed | Passed |
The instructions your model reads when the skill loads.
The modpack dev-log is the durable record of what the curator did to the modpack, in chronological order, with enough context for a future maintainer to understand why a change happened. This skill replaces the deleted templates/modpack/dev-log.md template by creating <project>/docs/dev-log.md at runtime, then appending entries as the modpack evolves.
| Use this skill when... | Result |
|---|---|
| The user says "log this", "add to dev log", "record what I did", or "note this change" | Append a dated entry to the project dev-log. |
| A mod was added, removed, replaced, upgraded, downgraded, patched, or moved in load order | Record what changed and why. |
| A conflict-audit session finished | Summarize the finding and link evidence from xedit-conflict-audit or xedit-automation output. |
| A CTD, freeze, missing asset, bad facegen, navmesh issue, or broken quest was investigated | Preserve the investigation result, even if the fix is not final. |
| A modpack release was cut | Add the curator-facing note and cross-link to writing-modpack-changelog. |
| The user made a manual decision that future agents must not re-litigate | Record the decision, context, and evidence. |
| Do not use this skill when... | Use instead |
|---|---|
| The user is preparing public release notes for players | writing-modpack-changelog |
| The user asks for a one-off explanation without wanting a project record | Answer directly. |
| The project root is unknown and the user refuses to identify it | Stop after explaining what is missing. |
| The entry would expose private notes, credentials, or personal information | Ask for a sanitized version first. |
| The request is to inspect or edit plugin records | xedit-automation or xedit-conflict-audit first, then log the result. |
<modpack_project_root>, use it.Data/, profiles/, or docs/, default to pwd and tell the user what default you used.<project>/docs/dev-log.md.
<project>/docs/ does not exist, create it.dev-log.md is missing, create it before appending.# <Project Name> Dev Logtest cases passed, vs 10 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.