agentleFS
Sign inStart free
shivae372shivae372/claude-bootstrap/.claude/skills/tips/SKILL.md

tips

Skill1 starsChanged 7 months agoApache-2.0View on GitHub

Surfaces a few high-leverage, context-aware tips for getting more out of Claude Code. Self-contained (no external data file). Invoked by /tips, by analyze-repo at the end of a scan, or when the user asks how to use Claude better.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. sonjh919/link-claude-skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository14 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    If USER_PROFILE.json exists, read tech_level and primary_goals to bias selection.

    line 16
  2. Very specific:

    Look at the project: are there tests?

    line 18
  3. Distinctive:

    Don't repeat the same tips every time.

    line 49

≈ “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

Purpose

Teach the user 3–5 high-impact habits, chosen to fit their tech level and what this project actually has. Tips live in this file (no external tips.json needed).

When To Use This

  • The user runs /tips or asks "how do I get better at this / what am I doing wrong?"
  • analyze-repo calls it at the end of a scan (show only 2–3, the most relevant)

Steps

  1. If USER_PROFILE.json exists, read tech_level and primary_goals to bias selection; otherwise assume tech_level 3.
  2. Look at the project: are there tests? agents? a long CLAUDE.md? a SESSION_STATE.md?
  3. Pick 3–5 tips from the catalog below, preferring ones the user can act on right now.
  4. Present them scannably: a bold category, the tip, and a one-line → example.

Tip Catalog

Tokens / context (tech 1–5)

  • 💡 Delegate exploration to the explorer sub-agent — its context is isolated, so reading a big codebase doesn't bloat your main session. → "explore where auth is handled"
  • 💡 Ask for targeted reads, not whole files. → "show lines 40–80 of server.ts", not "open server.ts"
  • 💡 /compact (or let the PreCompact hook checkpoint) before starting a new sub-task.

Workflow (tech 2–5)

  • 💡 /plan before building anything non-trivial — agree on scope first. → "/plan add OAuth login"
  • 💡 /ship before committing — it gates tests + review + security in one pass.
  • 💡 Keep SESSION_STATE.md current so a fresh session resumes instantly (the SessionStart hook reads it).

Quality (tech 3–5)

  • 💡 /review your diff before opening a PR; fix 🔴/🟠 findings first.
  • 💡 Put hard rules in hooks, not just CLAUDE.md — hooks are 100% reliable, prose is ~70%.

Prompting (tech 1–4)

  • 💡 State the goal AND the constraints. → "add caching, but don't change the public API"
  • 💡 When output is wrong, say what you expected — don't just say "no".

Safety (tech 1–5)

  • 💡 The safety-check + secret-detector hooks have your back, but still review destructive commands.
  • 💡 Never paste real secrets into chat — reference process.env.X / os.environ["X"] instead.

Notes

  • From analyze-repo, show only 2–3 and label them "Quick wins for this setup".
  • Don't repeat the same tips every time; vary by category.

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