All authors
Claude Skills by KrishP147
github.com/KrishP14730 skills0 installs14 views
- GradersNo description providedVotes: 0GitHub stars: 17
- Find Me A SkillSuggest which skill or workflow fits a task, with model and /effort per step and paste-ready commands; runs nothing. Use for "which skill should I use", "find me a skill", "how should I run this", "what model/effort for this".Votes: 0GitHub stars: 17
- Gap ScanSurvey one or more repos (code, commits, docs, tests, issues) and return a ranked, evidence-cited list of gaps, bugs, and extension ideas as issue-ready items. Read-only apart from its report. Use for "what's missing", "find gaps", "what should I work on in this repo".Votes: 0GitHub stars: 17
- Grill DocsGrill the user about a plan (same interview as grilling) and record it — Q→A transcript in grills/, each decision appended to the repo's decisions doc (both under skilleddocs/ by default). Use for "grill me and document it", "grill with docs".Votes: 0GitHub stars: 17
- GrillingGrill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.Votes: 0GitHub stars: 17
- Handoff AutoWrite a handoff document for a fresh session, callable by the model. Use from skills or subagents that must end a session unattended.Votes: 0GitHub stars: 17
- HandoffCompact the current conversation into a handoff document for another agent to pick up.Votes: 0GitHub stars: 17
- Consult PlanGrill a proposed change, deviation, or new idea against a repo's existing plan (issues, board, roadmap, decisions), then record the outcome. Use to pitch an idea; update-progress calls it for handoff deviations.Votes: 0GitHub stars: 17
- DivideSplit a GitHub issue or task into session-sized issues and put them on the board. Use when a task is too big for one session or remaining work must be split off.Votes: 0GitHub stars: 17
- Kanban SetupCreate a GitHub Projects kanban board for a repo and fill it with issues from documented work (planned, already done, or both).Votes: 0GitHub stars: 17
- NextShow the next work-session task from a repo's GitHub kanban board. Use when starting a work session or asking what to work on next.Votes: 0GitHub stars: 17
- Session HandoffEnd an implementation session that started from a GitHub issue — writes the handoff, records progress against the issue, moves the card.Votes: 0GitHub stars: 17
- Update ProgressVerify a session's handoff document and update the repo's docs and kanban board from it. Run in a fresh session after session-handoff.Votes: 0GitHub stars: 17
- LanesSet, increase, or decrease the parallel lanes of a meta-orchestrator run by grouping queued issues into file-disjoint streams, with a cost line and a confirm step. Use for "/lanes 3", "more lanes" / "go faster in parallel", "fewer lanes", or when meta-orchestrator setup reaches `parallel:`.Votes: 0GitHub stars: 17
- Meta OrchestratorRun a repo's backlog unattended as the orchestrator — planner, manager/implementer and verifier subagents per issue, merge gated on tests + CI, a ledger, and handoff to a fresh orchestrator on a budget. Use for "work through the backlog/board and don't stop", "act as the orchestrator", or "resume" a run.Votes: 0GitHub stars: 17
- PairRun one task (issue number or free text) in an isolated git worktree via a manager subagent that owns its implementer and retries; you push and open the PR at the end. Use for "implement issue N", "pair on this", or one task on any repo, forks included.Votes: 0GitHub stars: 17
- PonytailLazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.Votes: 0GitHub stars: 17
- Pr WatchWatch the user's open PRs to merge — read bot and human review threads, fix valid ones via pair, reply to or resolve the rest with evidence, report CI; every push, reply, and resolve gated on a yes. Use for "watch my PRs", "address the review comments", "drive this PR to merge".Votes: 0GitHub stars: 17
- Progress ReportWrite a short progress report of what an orchestrated or long session did since the last report (never overlapping): done, what worked, what didn't, concerns, decisions made for the user, manual steps. Use for "update doc", "what's been done", "write up progress".Votes: 0GitHub stars: 17
- RemindSet a reminder for when an account's session or weekly limit resets, when its usage drops under a percentage, or at a time; list or cancel them.Votes: 0GitHub stars: 17
- Repo ScrubScan a GitHub repo's full history for secrets and large files, scrub what the user picks, rewrite history safely, then flip it private → public.Votes: 0GitHub stars: 17
- Repo ShowcaseMake a repo public-facing on its working tree — README rewritten around outcome and demo, stale docs pruned, outdated claims fixed, secrets and private names found, GitHub metadata proposed — then hand off to /repo-scrub. Use for "showcase this repo", "polish the README for public", "prep for open-source or portfolio".Votes: 0GitHub stars: 17
- Score LoopRun an unattended experiment loop that hill-climbs one rerunnable numeric score — local grader-mirroring harness, one hypothesis per commit, keep only gains beyond the noise margin, auto-revert the rest, append-only results ledger; stops on budget, deadline or plateau. Use for "improve this score", "hill-climb a metric", "optimize until plateau/deadline", or "resume" / "status" / "summary" of a score loop.Votes: 0GitHub stars: 17
- Session BridgeCoordinate with another Claude Code session or agent on the same repo — snapshot its state, check for overlap, send it a gated message. Use for "check with / message the other session", "what's the other agent doing", "is anyone else touching this file or branch".Votes: 0GitHub stars: 17
- SitrepLive status of this session in ≤10 lines — what's running, git state, PRs + CI, asked vs done, what needs the user, and a SAFE/NOT SAFE close verdict. Use for "how's it going", "status update", "what's running", "can I close this".Votes: 0GitHub stars: 17
- Spend GateGate any billable action (GPU pods/instances, paid APIs or tiers, cloud credits) behind a cost estimate, a live balance check, and an explicit yes for that action. Use before any create/deploy on a paid provider (runpodctl, vultr-cli, aws/gcloud/az, modal, provider MCP create/deploy/run/start/update), any paid API call, or when spend-guard blocks one.Votes: 0GitHub stars: 17
- SwitchMove this conversation to another Claude account (the previous one, or one by name), or set up, add, remove, rename and list accounts.Votes: 0GitHub stars: 17
- Teammate BriefWrite an onboarding document for a person joining or picking up a project — what it is, setup steps verified by running them, env var names and where to get them, tasks with "done when", owners, don't-touch list. Use for "brief my teammate", "onboarding doc for X", "hand this project to someone".Votes: 0GitHub stars: 17
- Skill<What it is, then "Use when/for" + one phrase per distinct trigger. Loaded every session: aim for under ~50 words. See CONTRIBUTING §3.>Votes: 0GitHub stars: 17
- WayfinderPlan an effort too big for one session as a map of decision tickets (GitHub issue + sub-issues) and resolve them one per session until the way is clear, then hand off to divide.Votes: 0GitHub stars: 17