agentleFS
fmindfmind/dot/skills/dot-cli/SKILL.md

dot-cli

Skill13 starsChanged 4 days agoMITView on GitHub

Run dot: doctor, login, setup, status, pull, trust, secret, cache, prune, disk space, orphans, context, archives, agent token and cost stats.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Use dot for bounded repository operations, local diagnostics, and agent-session archives.

    line 15
  2. Very specific:

    Run documented commands directly: read the relevant --help only for an unfamiliar subcommand or after a usage error.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Dot CLI

Use dot for bounded repository operations, local diagnostics, and agent-session archives. The installed command and its --help own the active interface. Dot also owns workstation login, setup, and cache workflows; native CLIs retain credentials and provider behavior.

Workflow

  1. Run documented commands directly: read the relevant --help only for an unfamiliar subcommand or after a usage error. Global options precede subcommands.
  2. Select the operation's guide; previews authorize nothing: choose the guide for the requested operation; diagnostics and previews do not authorize login, cleanup, publication, or remote writes.
  3. Verify results at the requested level: local checks and hosted outcomes are separate evidence.

Task guides

<!-- guides:start -->
  • agent-usage: Report agent token usage, costs, and API equivalents from the session archive, with DuckDB exports.
  • authentication: Inspect and apply configured provider login, OAuth scopes, and account policy.
  • context: Measure discovery and instruction budgets in source or installed skill catalogs.
  • contracts: Resolve configuration, JSON output, exit codes, and session archive compatibility.
  • daily-workflows: Diagnose workstation health; run repository status and pull, folder trust, session sync and statistics, cleanup, and Fish completions.
  • disk-space: Audit workstation disk headroom, cache growth and shared tool versions before large downloads or builds.
  • orphans: Find files chezmoi deployed but no longer manages, then decide per path whether to keep, remove, or forget them.
<!-- guides:end -->

Workflow ownership

Use git-delivery for staged commits, github-pull-request for PRs, and repository mise tasks for releases. Use dot login and dot setup for configured provider policy (authentication); inspect gh auth, gcloud auth, and gws auth directly for native diagnostics, and use auth-status for a read-only login and expiry sweep. Skills own AI judgment; deterministic privacy and mutation boundaries still apply.

Documentation

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.