agentleFS
Sign inStart free
jiten-singh-shahijiten-singh-shahi/salesforce-claude-code/.cursor/skills/sessions/SKILL.md

sessions

Skill15 starsChanged 7 months agoMITView on GitHub

Use when managing Salesforce Claude Code session history. List, load, alias, and inspect saved Apex and org development sessions stored in ~/.claude/sessions/.

24 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use tool-rename-deprecation, add-policy and 8 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.
  • gitpod-ioSkill

    tool-rename-deprecation

    Ensure renamed built-in tool references preserve backward compatibility. Use when renaming a toolReferenceName, tool set referenceName, or any tool identifier. Run on ANY change to tool registration code. Covers legacyToolReferenceFullNames for tools and legacyFullNames for tool sets.

    Also in 5 projects that use this

  • OpenCortexIDESkill

    add-policy

    Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.

    Also in 4 projects that use this

  • gitpod-ioSkill

    agent-sessions-layout

    Agent Sessions workbench layout — covers the fixed layout structure, grid configuration, part visibility, editor modal, titlebar, sidebar footer, and implementation requirements. Use when implementing features or fixing issues in the Agent Sessions workbench layout.

    Also in 3 projects that use this

  • slopusSkill

    metrics-graphana

    Query and manage Grafana dashboards and Prometheus metrics for Happy infrastructure. Covers grafanactl CLI usage, direct Prometheus queries through Grafana proxy, and dashboard-as-code workflows. Use when user asks about metrics, dashboards, monitoring, Grafana, Prometheus, or wants to add/modify panels.

    Also in 3 projects that use this

  • slopusSkill

    control-flow

    Analyze and design control flows and data structures. Produces compact ASCII tree diagrams showing triggers, call chains, payload shapes, state mutations, and re-render effects. Use when user asks to diagram, trace, visualize, or design a flow or data structure.

    Also in 3 projects that use this

  • AnthropicSkill

    office-hours

    Set up and run Claude Code office hours, including the calendar event when the champion's own calendar connector allows it. Use when a champion wants a regular time for teammates to bring problems.

    Also in 3 projects that use this

  • +2 more from gitpod-io

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 21 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:

    Create a memorable alias for a session.

    line 52
  2. Distinctive:

    Delete an existing alias.

    line 61
  3. Distinctive:

    Use aliases for frequently referenced sessions

    line 124

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

Sessions — Session History Management

Manage Claude Code session history - list, load, alias, and inspect sessions stored in ~/.claude/sessions/.

When to Use

  • Listing all saved sessions to find a specific one
  • Loading a previous session by ID, date, or alias
  • Creating memorable aliases for frequently referenced sessions
  • Inspecting session metadata and statistics
  • Managing session aliases (create, remove, list)

Usage

/sessions [list|load|alias|info|aliases|help] [options]

/sessions help shows this usage guide.

Actions

List Sessions

Display all sessions with metadata, filtering, and pagination.

/sessions                              # List all sessions (default)
/sessions list                         # Same as above
/sessions list --limit 10              # Show 10 sessions
/sessions list --date 2026-03-18       # Filter by date
/sessions list --search apex           # Search by session ID

Load Session

Load and display a session's content (by ID or alias).

/sessions load <id|alias>             # Load session
/sessions load 2026-03-18             # By date
/sessions load apex-trig              # By short ID
/sessions load my-alias               # By alias name

Create Alias

Create a memorable alias for a session.

/sessions alias <id> <name>           # Create alias
/sessions alias 2026-03-18 trigger-work

Remove Alias

Delete an existing alias.

/sessions alias --remove <name>        # Remove alias
/sessions unalias <name>               # Same as above

Session Info

Show detailed information about a session.

/sessions info <id|alias>              # Show session details

List Aliases

Show all session aliases.

/sessions aliases                      # List all aliases

Arguments

  • list [options] - List sessions
    • --limit <n> - Max sessions to show (default: 50)
    • --date <YYYY-MM-DD> - Filter by date
    • --search <pattern> - Search in session ID
  • load <id|alias> - Load session content
  • alias <id> <name> - Create alias for session
  • alias --remove <name> - Remove alias
  • unalias <name> - Same as --remove
  • info <id|alias> - Show session statistics
  • aliases - List all aliases
  • help - Show this help

Examples

# List all sessions
/sessions list

# Create an alias for today's session
/sessions alias 2026-03-18 trigger-work

# Load session by alias
/sessions load trigger-work

# Show session info
/sessions info trigger-work

# Remove alias
/sessions alias --remove trigger-work

# List all aliases
/sessions aliases

Notes

  • Sessions are stored as markdown files in ~/.claude/sessions/
  • Session IDs can be shortened (first 4-8 characters usually unique enough)
  • Use aliases for frequently referenced sessions

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