agentleFS
Sign inStart free
beworkallbeworkall/agent-skills-security/skills/session-start/SKILL.md

session-start

Skill0 starsChanged 26 days agoMITView on GitHub

Use when the user's message is, or closely resembles (including typos/variants), "startsession" — e.g. "start session", "startsesion", "satrtsession", "start the session". Triggers a plain-language working mode for the rest of the conversation.

41 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use session-end, deploy-verify and 3 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.
  • jasonmichaelbell78-creatorSkill

    session-end

    Also in 11 projects that use this

  • 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

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

  • 0

    Common

    Most of the 34 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not match this skill for a message that merely mentions "session" in passing ("let's end this session") — only an explicit start-trigger …

    line 12
  2. Distinctive:

    Treat this message as a mode switch, not a task — don't ask "what do you mean?" Acknowledge briefly that session mode is on, then wait for …

    line 15
  3. Very specific:

    If a task matches one of the other installed skills (security-audit, secrets-handling, offline-first-workflow, safe-browser-agent, …

    line 18
  4. Distinctive:

    Don't re-explain this mode on every subsequent message in the same conversation — it stays active until the conversation ends or the user …

    line 21

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

When to Use

  • The user's message is the single word/phrase "startsession" in any casing
  • The user's message is a close typo or spaced variant of it (e.g. "start sesion", "startsesion", "satrt session") — match by intent, not exact spelling
  • Do not match this skill for a message that merely mentions "session" in passing ("let's end this session") — only an explicit start-trigger counts

Instructions

  1. Treat this message as a mode switch, not a task — don't ask "what do you mean?" Acknowledge briefly that session mode is on, then wait for (or use, if already given) the user's actual request.
  2. For the rest of this conversation, when the user describes a problem or goal in plain language (no explicit command name, no step-by-step instructions from them), do the work directly:
    • Pick the most reasonable interpretation and act — don't ask them to specify which skill, command, or exact syntax to use.
    • If a task matches one of the other installed skills (security-audit, secrets-handling, offline-first-workflow, safe-browser-agent, privacy-review), apply it automatically rather than asking the user to invoke it by name.
    • "Fix it" / "clear it" / "sort this out" are complete instructions — proceed using your best judgment on scope, then summarize what you changed.
  3. Still surface anything that genuinely needs a decision only the user can make (a destructive action, an ambiguous choice with real consequences) — plain-language mode means fewer procedural questions, not skipping judgment calls that matter.
  4. Don't re-explain this mode on every subsequent message in the same conversation — it stays active until the conversation ends or the user says otherwise.

Examples

User: "startsesion" Agent should: Respond briefly that it's ready, in plain-language mode — no need to specify exact commands from here.

User (later in the same conversation): "this login form feels off, clean it up" Agent should: Investigate the form, identify issues (validation, security, UX), fix them directly, and summarize the changes — without first asking the user to name which skill or exact steps to run.

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