ykdojo/claude-code-tips

Agent skills in the GitHub repository ykdojo/claude-code-tips, each with its code score out of 100.

45+ tips for getting the most out of Claude Code, from basics to advanced - includes a custom status line script and Claude Code running itself in a container. Also includes the dx plugin: skills for everyday dev workflows.

Repository score

60 / 100 C

Skills

9

Verified

0

Average skill score

60

GitHub stars

10,332

License

Not identified by GitHub

Open ykdojo/claude-code-tips on GitHub

9 skills in this repository

1. gha

   Analyze GitHub Actions failures and identify root causes

   64C
2. reddit-fetch

   Fetch content from Reddit via its JSON API using a browser session (DuckDuckGo-hop unlock). Use when accessing Reddit URLs, researching topics on Reddit, or when Reddit returns 40…

   64C
3. hn-summarize

   Fetch and summarize Hacker News / hckrnews.com top stories, articles, and their comment threads. Use when asked to summarize HN front-page stories, a specific HN story plus its di…

   63C
4. handoff

   Write or update a handoff document so the next agent with fresh context can continue this work.

   60C
5. version-check

   Recommend which Claude Code version to run, or whether to update. Use when asked which Claude Code version is best/safe, whether to update now, whether a recent release is buggy,…

   60C
6. review-claudemd

   Review recent conversations to find improvements for CLAUDE.md files.

   58C
7. private-github-search

   Full-text search across all of the user's GitHub repos (including private ones) using a local mirror and ripgrep. Use for "where did I put X", "which repo has X", or any search sp…

   57C
8. half-clone

   Clone the later half of the current conversation, discarding earlier context to reduce token usage while preserving recent work.

   55C
9. quarter-clone

   Clone the last quarter of the current conversation, discarding earlier context to reduce token usage while preserving recent work.

   55C

Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.