New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Automate Me

by tellahq in tellahq/opensession

A skill your agent uses for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works.

MITAuto-check passedAgent Workflows

Install Automate Me

skills CLI
$ npx skills add tellahq/opensession --skill automate-me -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tellahq/opensession automate-me --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tellahq/opensession.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pstack-suite/skills/automate-me .claude/skills/automate-me && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
automate-me
GitHub stars
394
Token cost
~1.9k tokens
SKILL.md length
1,058 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works.

  • Works in 7 steps: Check for an existing skill → Mine their history → Ask the user directly → …
  • Create/update/refresh my -mode skill
  • SKILL.md covers Flow, Guardrails, Evaluation and When not to use, plus 1 more section
  • Calls git

What it does

Automate Me is an agent skill from tellahq/opensession. Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via Open Session skill authoring + unslop, optionally pulling fresh evidence from recent transcripts.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Skill authoring. The licence is MIT.

When your agent uses it

  • Create/update/refresh my -mode skill
  • Turn/capture my preferences
  • Working style into a skill
  • Wanting agents to follow how the user works

Example prompts

  • “automate me”
  • “create/update/refresh my -mode skill”
  • “turn/capture my preferences or working style into a skill”
  • “/automate-me”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Check for an existing skill
  2. Mine their history
  3. Ask the user directly
  4. Cluster findings
  5. Draft the skill
  6. Iterate on prose
  7. Land it

What it can do on your machine

Read from SKILL.md and the folder at commit 068618d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Automate Me loads about 1.9k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 1,058 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~82
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tellahq/opensession at commit 068618d, republished under its MIT licence (© tellahq). 1,058 words, ~1,948 tokens.

Download SKILL.mdSave it as .claude/skills/automate-me/SKILL.md (or your agent's skills folder).
name
automate-me
description
Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via Open Session skill authoring + unslop, optionally pulling fresh evidence from recent transcripts.
disable-model-invocation
true

Automate me

A guided flow for turning the user's working conventions into a skill agents will follow. The output is one -mode skill tailored to them (e.g. jay-mode, priya-mode).

This skill orchestrates three others: an inline mining pass (see step 1), the repository skill conventions (authoring), and the unslop skill (prose discipline). It sequences them; it doesn't replace them.

Flow

0. Check for an existing skill

Look recursively for .agents/skills/**/*-mode/SKILL.md and .agents/skills/*-mode/SKILL.md matching the user's handle. Mode skills can live in a personal category directory (.agents/skills/<handle>/), not only at the top level. If one exists, confirm intent with one concise user question (unless they already said "update my skill" or similar):

  • Update the existing skill (default for repeat runs)
  • Start fresh (rare; ask why before doing it)

Update mode changes the rest of the flow:

  • Step 1 mines only history since the skill was last edited (git log -1 --format=%cI <path>).
  • Step 2 asks what's changed or missing, not what to capture from zero.
  • Step 4 edits the existing file in place. Preserve sections the user hasn't contradicted; revise ones with new evidence; add new sections only for genuinely new rules.
1. Mine their history

Discover the policy-gated Open Session session and history tools before fanning out. Identify sessions by exact id and explicit creator. Read only relevant transcript windows returned by those tools. Never scan session files, databases, or global transcript storage.

Survey recent agent conversations within that scope for recurring patterns. Run multiple ask-mode /pstack child sessions across slices of the gated history results (e.g. last 2-4 weeks, split into 3 slices so each has enough material). Each slice mining child session reads transcripts from the workspace-scoped path the parent provides, looks for the signals below, and returns a short structured list of patterns it saw with evidence pointers. Default signals worth hunting:

  • Response preferences (length, tone, format, "dumb it down" corrections)
  • Delegation habits (child sessions, models, specialized workflows, parallelism)
  • Verification posture (what "done" means; unit tests vs live repro; reviewers)
  • Code and prose discipline (style, principles cited, lint/format tools)
  • Process conventions (worktrees, commits, PRs, review/merge tooling)
  • Meta preferences (fixing skills mid-task, proposing new ones)

Cross-check across slices before elevating a signal. Patterns seen in 2+ slices are high-confidence; lone signals are weak and usually get dropped.

2. Ask the user directly

Mining misses intent that has not come up yet. Ask one or two concise user questions with 4-6 concrete options, then one optional free-form follow-up. Do not block on questions that an experiment or repository evidence can answer.

Don't dump 20 questions. Two structured rounds plus one open question is usually enough.

3. Cluster findings

Group the combined signals into sections. Common ones (use only what applies):

  • Response style: length, tone, format.
  • Autonomy: how much to do without asking; MCP tool use.
  • Understand first: which skills to reach for when scoping or investigating a change.
  • Delegation: default, parallelism, model-to-task, specialized workflows.
  • Prose / code discipline: principles, lint tools, style guides.
  • Review and verify: repro posture, verification skills, live-testing tools.
  • Process: git worktrees, commits, PRs, review/merge tooling.
  • Skills: skill-authoring habits, fix-the-skill-first, proposing new skills.

The poteto-mode skill shows the shape. Read it for granularity. Don't copy its content; the user's rules are not the same as poteto-mode's.

4. Draft the skill

Use the repository skill conventions to author the skill. Placement:

  • Path: preserve an existing mode skill's category. For a new mode, use .agents/skills/<handle>/<handle>-mode/SKILL.md when the repo has an established personal category for that handle; otherwise default to .agents/skills/<handle>-mode/SKILL.md in the project. A personal skill still needs an organization-controlled tracked source; do not write host-global skill directories.
  • Handle: the user's first name or chosen identifier.
  • Frontmatter description: trigger on their name + /<handle>-mode + "work in their style", not on generic keywords like "write code" or "review PR".
  • Frontmatter formatting: follow the repository's skill and YAML conventions. Keep description as one YAML scalar; quote it or use description: >- with indented continuation lines when punctuation or wrapping requires it.
  • Frontmatter disable-model-invocation: true by default. Mode skills are heavy and opinionated; they should only apply when the user explicitly invokes them (by name or slash command), not auto-trigger on description matching. Opt out only if the user explicitly wants their mode to apply on every turn.
Show full SKILL.md (354 more words)Show less
5. Iterate on prose

Apply the unslop skill and the repository's skill-writing guidelines to every line. Both apply to any agent-read prose, not just skills.

Show the draft to the user and take feedback. Expect multiple iterations. Cut ruthlessly; a mode skill is not a manual.

6. Land it

Follow the repository's own branch, commit, review, and publication workflow. Do not create a PR, push, or alter shared worktrees unless the active user and repository instructions authorize it.

Guardrails

  • Don't overfit to one conversation. A preference stated once and contradicted another time is noise. Require multiple instances before codifying it.
  • Don't be clever. Restating other skills' contents, inventing metaphors, or writing "poetic" prose for an agent reader is cost without benefit. Keep it operational.
  • Reference, don't inline. Other skills the user relies on should appear as path references, not pasted excerpts. Same for any principle docs they maintain elsewhere.
  • Keep sections minimal. Only add a section if the user has a specific, non-default rule there. "Communicate clearly" is not a section. "Short paragraphs. Tables when comparing options. Bullets only when items are genuinely parallel." is.
  • Name conventions generic. Use "the user" or "the human" in imperatives, not the author's first name. Others may read or adopt the skill.
  • Don't force symmetry. If a user has no process rules worth writing down, skip the Process section entirely. Sparse is fine; bloated is not.

Evaluation

A -mode skill is subjective output. A benchmark loop is not useful unless trigger accuracy or behavior can be graded objectively. Vibe-check with the user: does it read like them? Did it miss anything? Then ship.

Run a description-optimization loop only if the skill's trigger accuracy turns out to be a problem in practice.

When not to use

  • User wants a task-specific skill (not working conventions): the repository skill conventions alone, no mining required.
  • User wants to capture one narrow workflow (e.g. "how I write commit messages"): that's a regular skill, not a mode skill.

Reference files

  • The poteto-mode skill: example of the output shape.
  • The unslop skill: prose discipline for every line.
  • Repository skill conventions: authoring process and writing guidelines.

© tellahq, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/pstack-suite/skills/automate-me of tellahq/opensession.

Open the folder on GitHubat commit 068618d

Compare with similar skills

Automate Me next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Automate Me compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Automate Me this skilltellahq/opensession394—~1.9kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79689 repos~8.2kAutomated safety check: PassApache-2.0
Claude Code Skill Developer Guidediet103/claude-code-infrastructure-showcase10k11 repos~3.5kAutomated safety check: PassMIT
Darwin Skill Optimizeralchaincyf/darwin-skill6.2k1 repos~4.7kAutomated safety check: PassMIT
Claude Code Command Developmentanthropics/claude-plugins-official38k10 repos~4.8kAutomated safety check: PassApache-2.0
Claude Code Plugin Structureanthropics/claude-plugins-official38k10 repos~3.4kAutomated safety check: PassApache-2.0

Similar skills

  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    796 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Skill Developer Guide

    diet103/claude-code-infrastructure-showcase

    A guide to creating and managing Claude Code skills with auto-activation: skill-rules.json triggers, hooks, enforcement levels, YAML frontmatter and progressive disclosure.

    10k GitHub starsUsed in 11 repos~3.5k tokens
    Agent WorkflowsAuto-check passed

  • Darwin Skill Optimizer

    alchaincyf/darwin-skill

    Scores SKILL.md files on a nine-dimension rubric, then improves them in a keep-or-revert loop with independent judge agents, test prompts, git history and human checkpoints.

    6.2k GitHub starsUsed in 1 repo~4.7k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Command Development

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code slash commands: Markdown files with YAML frontmatter, arguments, file references, bash context and interactive prompts.

    38k GitHub starsUsed in 10 repos~4.8k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Plugin Structure

    anthropics/claude-plugins-official

    Official

    Explains the directory layout, plugin.json manifest and component organization of a Claude Code plugin, including auto-discovery and portable paths.

    38k GitHub starsUsed in 10 repos~3.4k tokens
    Agent WorkflowsAuto-check passed

  • Skill Release Gate

    rohitg00/ai-engineering-from-scratch

    Evaluates an Agent Skill bundle before release for structure, trigger quality, artifact improvement, script correctness, safety, installed-tree integrity and host portability.

    66k GitHub stars~1k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from tellahq/opensession

All 15 skills in this repo

  • Effect TS

    tellahq/opensession

    Write idiomatic Effect v4 TypeScript verified against the pinned effect@4.0.0-rc.112 source.

    394 GitHub stars~3.7k tokensUpdated today
    Auto-check passed

  • Reflect

    tellahq/opensession

    Spawn three parallel review child sessions over the active transcript, surface learnings, and route each to a concrete edit on an existing skill.

    394 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Show Me

    tellahq/opensession

    Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.

    394 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • PR Autofix

    tellahq/opensession

    Auto-fix a PR — address ALL reviewers' open feedback + failing CI, push, and reply in each addressed thread with honest attribution

    394 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

  • Swarm

    tellahq/opensession

    Fan out N parallel workers, drain them, and return one report.

    394 GitHub stars~609 tokensUpdated today
    Auto-check passed

  • Verify Opensession

    tellahq/opensession

    Drive the Open Session web UI against an isolated demo server and capture proof for session, workspace, automation, goal, archive, or settings changes.

    394 GitHub stars~1.8k tokensUpdated today
    Auto-check passed

Categories

Questions about Automate Me

What does Automate Me do?

A skill your agent uses for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Automate Me is an agent skill from tellahq/opensession. Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works.

When should I use Automate Me?

Automate Me fits situations like: create/update/refresh my -mode skill; turn/capture my preferences; working style into a skill; wanting agents to follow how the user works.

How do I install Automate Me in Claude Code?

Run `npx skills add tellahq/opensession --skill automate-me -a claude-code`. Or copy the skill folder (.agents/skills/pstack-suite/skills/automate-me in tellahq/opensession) into .claude/skills/automate-me in your project. Claude Code loads it when a task matches its description.

How do I install Automate Me in Codex?

Run `npx skills add tellahq/opensession --skill automate-me -a codex`. Or copy the skill folder (.agents/skills/pstack-suite/skills/automate-me in tellahq/opensession) into .agents/skills/automate-me in your project. Codex loads it when a task matches its description.

Can I use Automate Me in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tellahq/opensession --skill automate-me -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/automate-me, .gemini/skills/automate-me, .github/skills/automate-me and .opencode/skills/automate-me in your project.

What does Automate Me need to run?

Going by SKILL.md and its folder, Automate Me needs the command-line tools its instructions call (git).

Does Automate Me access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Automate Me safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Automate Me use?

Automate Me is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Automate Me use?

About 1.9k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Automate Me?

Skills that share tags, products or a category with Automate Me: Skill Creator (Azure/azqr, 796 stars), Claude Code Skill Developer Guide (diet103/claude-code-infrastructure-showcase, 10k stars), Darwin Skill Optimizer (alchaincyf/darwin-skill, 6.2k stars) and Claude Code Command Development (anthropics/claude-plugins-official, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Automate Me?

tellahq (a GitHub organization) maintains it in tellahq/opensession, which has 394 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 9, 2026.

Source: tellahq/opensession on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.