L2 Assess · github trending · Aug 8, 2026

mattpocock/skills

deferhigh confidence

01 · Fit to Stack

strong fit

field-notes already runs on Claude Code CLAUDE.md and skills, which is the exact mechanism mattpocock/skills packages - a directory of discrete, composable instruction files consumed by an agentic CLI. Adopting the pattern requires no new tooling, languages, or infra, just reorganizing files already in the repo.

02 · Fit to Vision

partial fit

This is internal tooling hygiene, not a user-facing capability - it fits the 'practical over experimental' preference but doesn't itself improve any workflow the operator uses day to day. Its value is indirect: it derisks and speeds up the L3/L4 skill-building work that's already in progress, rather than shipping something new.

Implementation Options

01Split CLAUDE.md into task-scoped skill files

field-notes4-8 hoursmedium risk

Break the monolithic field-notes CLAUDE.md into discrete files (e.g. enrichment-workflow.md, block-schema.md, pipeline-stage-advance.md), each independently loadable and following a one-skill-one-job convention. Update any CCR prompts, stage triggers, or n8n workflow steps that currently reference the single file.

+Reduces per-invocation context load for CCR stages that only need part of the document

+Makes it easier to add L3/L4 skills later without further bloating one file

-Real refactor risk - CCR triggers and pipeline stages that reference the monolithic file need to be found and updated

-Testing every pipeline stage after the split is real time for a solo operator on an already-working, mostly-unattended system

02Reference-only: adopt naming convention for new skills

field-notes1-2 hourslow risk

Leave the existing CLAUDE.md untouched. When building the still-pending L3 planner and L4 executor skills, structure just those new files using Pocock's taxonomy (task-type naming, consistent invocation header, one skill does one job) as a lightweight style guide.

+Zero risk to the working pipeline - no changes to anything currently running

+Captures the useful part (naming and structure discipline) at almost no cost

-Doesn't reduce the current CLAUDE.md's context load

-The existing monolithic sections still need eventual cleanup, just deferred

01 · Value

The reorg option could measurably shrink per-stage context in CCR calls once field-notes has several skills defined. The reference-only option costs almost nothing and sets a naming convention that keeps the L3/L4 skills from compounding the same disorganization as they're added.

02 · Why It Matters

field-notes's own skill set is about to grow with the L3 planner and L4 executor. The real question this item raises isn't whether Pocock's repo is good - it's whether field-notes's current single-file CLAUDE.md structure scales past one more stage before it needs to be split anyway.

03 · What Implementation Looks Like

For the reference-only option: no changes to the existing CLAUDE.md. When authoring the L3/L4 CCR prompts, name and header them consistently and add a short paragraph at the top of CLAUDE.md documenting the convention for future skills. The minimal v1 is a naming and structure decision applied going forward, not a migration of existing content.