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

Later

by jackfranklin in jackfranklin/dotfiles

Log items to come back to later — bugs found mid-task, feature ideas, project feedback — as GitHub Issues.

MITAuto-check passedDevelopment

Install Later

skills CLI
$ npx skills add jackfranklin/dotfiles --skill later -a claude-code

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

GitHub CLI
$ gh skill install jackfranklin/dotfiles later --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/jackfranklin/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude/skills/later .claude/skills/later && 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
later
GitHub stars
255
Token cost
~767 tokens
SKILL.md length
402 words
Files
1
Skills in repo
19
Repo updated
First seen
Licence
MIT

At a glance

Log items to come back to later — bugs found mid-task, feature ideas, project feedback — as GitHub Issues.

  • Works in 4 steps: Run gh issue list --state open to get… → Present the titles and ask which to… → Run gh issue view for items being… → …
  • The user asks to log
  • SKILL.md covers GitHub body safety — mandatory, Before anything else, Logging an item and Listing open items, plus 4 more sections
  • Calls gh

What it does

Later is an agent skill from jackfranklin/dotfiles. Log items to come back to later — bugs found mid-task, feature ideas, project feedback — as GitHub Issues. Use when the user asks to log, list, view, or work through items saved for later.

Its SKILL.md is about 770 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 Development. It works with GitHub. The repository describes itself as: My dotfiles for my dev environment, compromising of tmux, vim, zsh and git. The licence is MIT.

When your agent uses it

  • The user asks to log
  • Work through items saved for later

Example prompts

  • “/later”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Run gh issue list --state open to get open items.
  2. Present the titles and ask which to tackle.
  3. Run gh issue view for items being actively discussed, then follow the discuss-before-implementation rule above.
  4. After an item is resolved, run gh issue close .

What it can do on your machine

Read from SKILL.md and the folder at commit 48208f5. 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:

    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use gh, 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

Later loads about 767 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 402 words of instructions outside code blocks.

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

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 jackfranklin/dotfiles at commit 48208f5, republished under its MIT licence (© jackfranklin). 402 words, ~767 tokens.

Download SKILL.mdSave it as .claude/skills/later/SKILL.md (or your agent's skills folder).
name
later
description
Log items to come back to later — bugs found mid-task, feature ideas, project feedback — as GitHub Issues. Use when the user asks to log, list, view, or work through items saved for later.
disable-model-invocation
true

Use gh to manage backlog items as GitHub Issues in the current repo.

GitHub body safety — mandatory

Never pass issue Markdown through a shell-quoted --body argument. Markdown commonly contains backticks, $, or command examples; in double-quoted Bash strings those can execute shell command substitution and leak their output into GitHub.

  • Always write issue bodies to a temporary file outside the repository with the file-writing tool, then use gh ... --body-file /tmp/<descriptive>.md.
  • Never use --body "...", --body "$(...)", backticks inside shell strings, or an unquoted heredoc for issue content.
  • If a shell heredoc is unavoidable, its delimiter must be single-quoted: <<'EOF'.
  • After publishing Markdown, verify the stored body is literal Markdown. If it contains shell output or credentials, immediately delete or replace the comment, stop work, and tell the user to rotate exposed credentials.

Before anything else

Verify there is a GitHub remote: gh repo view --json nameWithOwner. If it fails, stop and tell the user there is no GitHub remote — they need to be in a GitHub-backed repo to use this skill.

Logging an item

Write /tmp/<repository>-issue-<slug>.md with the file-writing tool, then run:

gh issue create --title "<title>" --body-file /tmp/<repository>-issue-<slug>.md

Add labels if helpful (e.g. --label bug), but don't create labels that don't exist yet — only use labels already present in the repo.

Before creating, run gh issue list --search "<title>" to check for duplicates. If a near-match exists, show it to the user and ask whether to update that issue or create a new one.

Listing open items

gh issue list --state open
Show full SKILL.md (164 more words)Show less

Viewing an item

gh issue view <number>

Never jump straight into implementation after reading an issue. After gh issue view, always: summarise the issue in your own words, investigate the relevant code enough to explain why it happens (root cause, not just symptoms), then present your thoughts — options, tradeoffs, a recommendation if you have one — and ask the user how they'd like to proceed. Only start editing code once the user has confirmed a direction. This applies even if the fix looks small or obvious.

Closing an item

gh issue close <number>

Working through items

  1. Run gh issue list --state open to get open items.
  2. Present the titles and ask which to tackle.
  3. Run gh issue view <number> for items being actively discussed, then follow the discuss-before-implementation rule above.
  4. After an item is resolved, run gh issue close <number>.

Priorities

If the user specifies priority, map it to labels if they exist in the repo (priority: high, priority: medium, priority: low). Otherwise note priority in the issue body.

© jackfranklin, 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 claude/skills/later of jackfranklin/dotfiles.

Open the folder on GitHubat commit 48208f5

Compare with similar skills

Later 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.

Later compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Later this skilljackfranklin/dotfiles255—~767Automated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Setup Matt Pocock Skillsbestofjs/bestofjs3.1k20 repos~1.7kAutomated safety check: PassMIT
Summarise Ecosystem Resultsastral-sh/ruff50k1 repos~2.2kAutomated safety check: PassMIT

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Setup Matt Pocock Skills

    bestofjs/bestofjs

    Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.

    3.1k GitHub starsUsed in 20 repos~1.7k tokens
    DevelopmentAuto-check passed

  • Summarise Ecosystem Results

    astral-sh/ruff

    Official

    A skill your agent uses when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem…

    50k GitHub starsUsed in 1 repo~2.2k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

More from jackfranklin/dotfiles

All 19 skills in this repo

  • GitHub Code Review

    jackfranklin/dotfiles

    Perform a thorough, read-only review of one GitHub pull request.

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

  • Adr

    jackfranklin/dotfiles

    Capture an Architecture Decision Record (ADR) for a significant decision made in the current project.

    255 GitHub stars~962 tokensUpdated today
    Auto-check passed

  • Jack References

    jackfranklin/dotfiles

    Manage Jack's personal technical reference library at ~/git/references.

    255 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • New Deno App

    jackfranklin/dotfiles

    Scaffold a new Deno 2 + Hono + Deno KV + Eta + HTMX app with password auth and PWA support.

    255 GitHub stars~3.6k tokensUpdated today
    Auto-check: notes

  • Resolve Merge Conflict

    jackfranklin/dotfiles

    A skill your agent uses when you need to resolve an in-progress git merge/rebase conflict.

    255 GitHub starsUsed in 23 repos~427 tokens
    Auto-check passed

  • Writing Great Skills

    jackfranklin/dotfiles

    Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

    255 GitHub starsUsed in 15 repos~2.2k tokens
    Auto-check passed

Works with

Categories

Questions about Later

What does Later do?

Log items to come back to later — bugs found mid-task, feature ideas, project feedback — as GitHub Issues. Later is an agent skill from jackfranklin/dotfiles. Log items to come back to later — bugs found mid-task, feature ideas, project feedback — as GitHub Issues.

When should I use Later?

Later fits situations like: the user asks to log; work through items saved for later.

How do I install Later in Claude Code?

Run `npx skills add jackfranklin/dotfiles --skill later -a claude-code`. Or copy the skill folder (claude/skills/later in jackfranklin/dotfiles) into .claude/skills/later in your project. Claude Code loads it when a task matches its description.

How do I install Later in Codex?

Run `npx skills add jackfranklin/dotfiles --skill later -a codex`. Or copy the skill folder (claude/skills/later in jackfranklin/dotfiles) into .agents/skills/later in your project. Codex loads it when a task matches its description.

Can I use Later 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 jackfranklin/dotfiles --skill later -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/later, .gemini/skills/later, .github/skills/later and .opencode/skills/later in your project.

What does Later need to run?

Going by SKILL.md and its folder, Later needs the command-line tools its instructions call (gh).

Does Later access the network?

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

Is Later 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 Later use?

Later 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 Later use?

About 767 tokens (SKILL.md is roughly 3.1k 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 Later?

Skills that share tags, products or a category with Later: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Greploop (onyx-dot-app/onyx, 32k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Later?

jackfranklin (a GitHub user) maintains it in jackfranklin/dotfiles, which has 255 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 7, 2026.

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