agentleFS
Sign inStart free
yogsoth-aiyogsoth-ai/context-management/skills/context-init/SKILL.md

context-init

Skill2 starsChanged 5 months agoApache-2.0View on GitHub

Create a new context file for a research Phase. Called once at Phase start to initialize the file that subsequent context-checkpoint calls will append to. Use this skill whenever a new research Phase begins and a fresh context file is needed.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. lifan-builds/context-harness★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a new context file for a research Phase.

    line 8
  2. Distinctive:

    Run the timestamp script to get the current time:

    line 21
  3. Very specific:

    Create the file at: context/<timestamp>-<topic-slug>.md

    line 38
  4. Distinctive:

    Write the initial content:

    line 40
  5. Very specific:

    If context/INDEX.md does not exist, create it:

    line 60
  6. Distinctive:

    Add a new row for this file:

    line 69
  7. Distinctive:

    If a context file for the current Phase already exists (check INDEX.md for a matching Phase name created in the current session), skip …

    line 77

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Context Init

Create a new context file for a research Phase. One file per Phase — subsequent checkpoints append to this file.

When Called

Once at the beginning of each research Phase, imported by the plan file:

step: "import context-management:context-init"

Execution Protocol

Step 1: Get Timestamp

Run the timestamp script to get the current time:

python <context-management-repo-path>/scripts/timestamp.py

Output format: yyyy-mm-dd-hh-mm (e.g., 2026-05-16-14-30)

Step 2: Determine Topic Slug

Based on the current Phase context, decide a topic slug:

  • Lowercase, hyphen-separated
  • Reflects the Phase name or research topic
  • Examples: lit-survey, gap-analysis, protein-folding-ideation

Step 3: Create Context File

Create the file at: context/<timestamp>-<topic-slug>.md

Write the initial content:

# <Phase Topic>

> Created: <yyyy-mm-dd hh:mm>
> Topic: <Research Topic>
> Phase: <Phase Name>

## Plan Context

<Plan excerpt for this Phase: objectives, expected outputs, constraints, relationship to other Phases in the pipeline>

The Plan Context section should contain the relevant plan excerpt describing this Phase's goals, expected deliverables, and how it connects to the broader research pipeline.

No mid-paragraph line breaks: Write each prose paragraph as a single continuous line. Do not insert newlines inside a paragraph to wrap it at a column width. Newlines are only for separating paragraphs, list items, headings, and fenced code blocks. This applies to the Plan Context written here and to all content appended later by context-checkpoint.

Step 4: Initialize or Update INDEX.md

If context/INDEX.md does not exist, create it:

# Context Index

| File | Phase | Topic | Checkpoints | Last Updated |
|------|-------|-------|-------------|--------------|

Add a new row for this file:

| <filename> | <Phase Name> | <Research Topic> | 0 | <yyyy-mm-dd hh:mm> |

Idempotency

If a context file for the current Phase already exists (check INDEX.md for a matching Phase name created in the current session), skip creation and return the existing file path.

Output

The file path of the created (or existing) context file. This path is used by subsequent context-checkpoint calls within the same Phase.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free