agentleFS
Sign inStart free
ravindu57ravindu57/SCML/.claude/skills/session-start/SKILL.md

session-start

Skill0 starsChanged 26 days agoApache-2.0View on GitHub

Start a work session on SCML — load current state, declare the session role, pick exactly one backlog item.

39 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use deploy-verify, reflect and 2 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.
  • danielarif26Skill

    deploy-verify

    Verify a Vercel deployment actually went live and serves the correct production domain. Self-improving: reads its own run history before checking and logs the outcome after. Use when the user asks "did you deploy?", "is it live?", "verify the deploy", "check vercel", or after any Vercel deploy. Part of the Agentic OS (Level 1 backbone).

    Also in 3 projects that use this

  • Microsoft AzureSkill

    reflect

    Learning capture system that extracts HIGH/MED/LOW confidence patterns from conversations to prevent repeating mistakes. Use after user corrections ("no", "wrong"), praise ("perfect", "exactly"), or when discovering edge cases. Complements .squad/agents/{agent}/history.md and .squad/decisions.md.

    Also in 4 projects that use this

  • ibahgatSkill

    autopilot

    Run autonomous multi-stage execution loops until acceptance criteria pass or blockers are reached.

    Also in 3 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 32 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the current-state block and the latest log entry in PROGRESS.md.

    line 10
  2. Very specific:

    Run scripts/check_frozen.sh.

    line 11
  3. Very specific:

    Run the test suite with the env prefix from CLAUDE.md and note the pass count.

    line 12
  4. Very specific:

    Read feature_list.json. If an item id was given, use it.

    line 13
  5. Very specific:

    Read the .claude/rules/*.md files that cover the paths the item touches, and the ADRs in docs/DECISIONS.md that mention it.

    line 14

“Common” is measured: kept by at least 6 in 10 of the 32 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

Session role: $ARGUMENTS

  1. Read the current-state block and the latest log entry in PROGRESS.md.
  2. Run scripts/check_frozen.sh. If it fails, stop and report; do not continue.
  3. Run the test suite with the env prefix from CLAUDE.md and note the pass count. If it differs from PROGRESS.md, say so before anything else.
  4. Read feature_list.json. If an item id was given, use it; otherwise propose the highest-priority item with passes: false that suits this role (see docs/recovery/ROLE_PLAN.md for which roles do what). Show its acceptance criteria.
  5. Read the .claude/rules/*.md files that cover the paths the item touches, and the ADRs in docs/DECISIONS.md that mention it.
  6. State, in under 10 lines: the role, the one item, its acceptance criteria, which frozen paths are nearby, and whether it costs money (paid LLM runs need a cost estimate and approval first).
  7. For anything but a Conversationalist session, enter plan mode and wait for approval before changing files.

Stay in the declared role. If the work needs another role, say so and suggest ending the session.

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