agentleFS
mag123cmag123c/toktrack/.claude/skills/next/SKILL.md

next

Skill196 starsChanged 13 days agoMITView on GitHub

Session start - check progress, suggest next task

42 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use quick, project and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • codebycoreySkill

    quick

    Quick start a change with minimal interaction. Use when fast-tracking a straightforward change that needs proposal, design, and tasks in one step.

    Also in 3 projects that use this

  • BugRogerSkill

    project

    Project lifecycle management. Dispatches to Ada.

    Also in 3 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 9 projects that use this

  • MicrosoftSkill

    cleanup

    Also in 4 projects that use this

  • genomewalkerSkill

    explore

    RLM-style recursive memory exploration - dynamically navigate the memory graph

    Also in 3 projects that use this

  • GoogleSkill

    critique

    Expertise in auditing and fixing repository scripts and GitHub Actions workflows to ensure technical robustness and security.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 37 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If no planning files → infer from git log + code state

    line 61
  2. Distinctive:

    Keep output concise (5-10 lines)

    line 62
  3. Distinctive:

    Always suggest /clarify connection

    line 63

“Common” is measured: kept by at least 6 in 10 of the 37 edited versions of this file we could read. “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

Next

Flow

Read Planning → Git Log → Analyze → Present → Suggest /clarify

Execution

  1. Read Planning
    # Read ONLY the latest planning file (by date prefix YYYYMMDD-)
    # e.g., 20260205-improvements.md > 20260128-cli-parsers.md
    # Check checkbox status: [ ] incomplete, [x] complete
  2. Git Log
    git log --oneline -5
    git status --short
  3. Analyze
    • Identify current phase
    • Count completed/total tasks
    • Identify next priority task
  4. Present (table format)
    PhaseStatusProgress
    Phase 0✅5/5
    Phase 1🔄3/4
  5. Suggest
    • Summarize next task
    • Suggest running /clarify

Output Format

## Current Status
- Phase: {current_phase}
- Progress: {completed}/{total} tasks

## Next Task
**{task_id}: {task_name}**
{brief_description}

## Action
Run `/clarify` to start: {task_summary}

Rules

  • Read only the latest dated planning file (highest YYYYMMDD- prefix)
  • If no planning files → infer from git log + code state
  • Keep output concise (5-10 lines)
  • Always suggest /clarify connection

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.