Deep Dive
byungjunjang/jangpm-meta-skills
Socratic interview skill to deepen a spec or refine an existing agent blueprint.
A skill your agent uses when starting any conversation in a loopkit-enabled project - establishes how to find and use loopkit's 49 skills, requiring skill invocation before ANY response including…
$ npx skills add Archive228/loopkit --skill using-loopkit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Archive228/loopkit using-loopkit --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Archive228/loopkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/using-loopkit .claude/skills/using-loopkit && rm -rf skills-srcUse ~/.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/
Install the "using-loopkit" agent skill from https://github.com/Archive228/loopkit/tree/main/skills/using-loopkit into .claude/skills/using-loopkit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-loopkit", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Archive228/loopkit/tree/main/skills/using-loopkitType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Archive228/loopkit --skill using-loopkit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Archive228/loopkit using-loopkit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Archive228/loopkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/using-loopkit .agents/skills/using-loopkit && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "using-loopkit" agent skill from https://github.com/Archive228/loopkit/tree/main/skills/using-loopkit into .agents/skills/using-loopkit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-loopkit", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Archive228/loopkit --skill using-loopkit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Archive228/loopkit using-loopkit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Archive228/loopkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/using-loopkit .cursor/skills/using-loopkit && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "using-loopkit" agent skill from https://github.com/Archive228/loopkit/tree/main/skills/using-loopkit into .cursor/skills/using-loopkit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-loopkit", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Archive228/loopkit.git --path skills/using-loopkit--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Archive228/loopkit --skill using-loopkit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Archive228/loopkit using-loopkit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Archive228/loopkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/using-loopkit .gemini/skills/using-loopkit && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "using-loopkit" agent skill from https://github.com/Archive228/loopkit/tree/main/skills/using-loopkit into .gemini/skills/using-loopkit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-loopkit", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Archive228/loopkit using-loopkitInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Archive228/loopkit --skill using-loopkit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Archive228/loopkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/using-loopkit .github/skills/using-loopkit && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "using-loopkit" agent skill from https://github.com/Archive228/loopkit/tree/main/skills/using-loopkit into .github/skills/using-loopkit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-loopkit", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Archive228/loopkit --skill using-loopkit -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Archive228/loopkit using-loopkit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Archive228/loopkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/using-loopkit .opencode/skills/using-loopkit && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "using-loopkit" agent skill from https://github.com/Archive228/loopkit/tree/main/skills/using-loopkit into .opencode/skills/using-loopkit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-loopkit", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
using-loopkitA skill your agent uses when starting any conversation in a loopkit-enabled project - establishes how to find and use loopkit's 49 skills, requiring skill invocation before ANY response including…
Using Loopkit is an agent skill from Archive228/loopkit. Use when starting any conversation in a loopkit-enabled project - establishes how to find and use loopkit's 49 skills, requiring skill invocation before ANY response including clarifying questions.
Its SKILL.md is about 1.4k 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 Agent Workflows, covering Requirements gathering. The repository describes itself as: 33 battle-tested skills + minimal .claude harness for any coding agent (Claude Code, Cursor, Codex, Gemini CLI). The licence is MIT.
Read from SKILL.md and the folder at commit 5ae033e. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Using Loopkit loads about 1.4k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 570 words of instructions outside code blocks.
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.
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.
The full file from Archive228/loopkit at commit 5ae033e, republished under its MIT licence (© Archive228). 570 words, ~1,357 tokens.
.claude/skills/using-loopkit/SKILL.md (or your agent's skills folder).<EXTREMELY-IMPORTANT>
If you think there is even a 1% chance a loopkit skill applies to what you are doing, INVOKE it.
IF A SKILL APPLIES, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
This overrides "just answer quickly" instincts. Not negotiable.
</EXTREMELY-IMPORTANT>
Invoke relevant skills BEFORE any response or action — including clarifying questions, exploring the codebase, or reading files. If it turns out wrong for the situation, drop it.
Then announce "Using [skill] to [purpose]" and follow the skill exactly. If it has a checklist, create a todo per item.
Skills are files at .claude/skills/<name>/SKILL.md. Each has YAML frontmatter with name and description (the description is a trigger phrase, not a summary). Load a skill by reading its SKILL.md when its trigger matches your task.
| Task shape | First skill |
|---|---|
| "Fix this bug" / test failing / crash | systematic-debugging, then read-the-trace |
| "It broke between two commits" | bisect-regression |
| "Flaky test" | flaky-hunter |
| "Add a feature" / write anything new | spec-first, then write-failing-test-first |
| "Refactor" / dead code / deep nesting | kill-dead-code, simplify, reduce-nesting |
| About to claim done / commit / open PR | adversarial-verify + verification-before-completion + self-eval-bias |
| Review a diff | adversarial-verify, pr-from-diff |
| Frontend / UI work | design-system, a11y-pass, loading-empty-error-states |
| Security touch | owasp-review, authz-check, input-validation, secret-scan, dependency-audit |
| Data / SQL / migrations | sql-review, migration-writer, schema-diff |
| Docs / changelog / README | changelog-from-diff, decision-record, readme-audit |
| Git ops | clean-commits, pr-from-diff, rebase-safely, revert-surgical |
| Test suite gaps | coverage-gaps, contract-test |
| Running out of context | context-budget, tool-restraint |
| Parallel work | subagent-fanout |
| Starting a fresh project / major feature | planner-spec-expand, then feature-list-json, then init-script-contract |
| Bootstrapping into an existing multi-session project | progress-reading-protocol |
| Entering an implementation sprint | sprint-contract |
| Calibrating a reviewer / evaluator | evaluator-calibration |
| New Claude/Sonnet/Opus model landed | harness-stripping |
Full list: ls .claude/skills/.
| Thought | Reality |
|---|---|
| "This is just a simple question" | Questions are tasks. Check first. |
| "Let me explore the codebase first" | Skills tell you HOW to explore. Check first. |
| "I remember this skill" | Skills evolve. Read the current SKILL.md. |
| "The skill is overkill" | Simple things become complex. Use it. |
| "I'll just do this one thing first" | Check BEFORE doing anything. |
| "Tests pass, we're good" | verification-before-completion says: run the exact command, read the output, then claim. |
| "I'll do both features while I'm in here" | single-feature-discipline says: one per session. Never two. |
| "The reviewer will let this slide" | self-eval-bias says: assume it will confidently praise. Calibrate first. |
Process skills first (spec-first, systematic-debugging, planner-spec-expand, sprint-contract), then implementation skills (design-system, sql-review, etc.), then finishers (adversarial-verify, verification-before-completion, self-eval-bias, clean-commits).
planner-spec-expand → feature-list-json → sprint-contract → domain skills → adversarial-verify.systematic-debugging → read-the-trace → fix → verification-before-completion.progress-reading-protocol → sprint-contract → work.Every new skill in loopkit ships as a folder with four required files. No exceptions — a skill without these is a draft, not a release.
skills/<skill-name>/
SKILL.md # the skill itself (frontmatter + procedure)
POST.md # ~200-word X-thread-shaped explainer
evidence/
before.md # verbatim transcript WITHOUT the skill loaded
after.md # same prompt WITH the skill loadedSKILL.md — routed on its frontmatter description. Body under ~150 lines.POST.md — the announcement thread. Copy from template/POST.md, fill in every placeholder before publishing.evidence/before.md + evidence/after.md — one real task, both transcripts. The before/after pair is the receipt that the skill actually changes behaviour. If you cannot produce it, the skill is not ready; land it as a draft and merge once the evidence is real.Bootstrap a new skill by copying template/ verbatim:
cp -r template skills/<skill-name>Then edit SKILL.md, write POST.md, and capture the before/after pair.
CLAUDE.md, AGENTS.md, and direct user requests override loopkit skills. Only skip a skill workflow when the user has explicitly said to.
© Archive228, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/using-loopkit of Archive228/loopkit.
Open the folder on GitHubat commit 5ae033e
Using Loopkit 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Using Loopkit this skillArchive228/loopkit | 755 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Deep Divebyungjunjang/jangpm-meta-skills | 120 | — | ~2.5k | Automated safety check: Pass | None | |
| Grillingpietheinstrengholt/rssmonster | 564 | 31 repos | ~510 | Automated safety check: Pass | MIT | |
| Grill With Docsmeain/dotfiles | 285 | 20 repos | ~875 | Automated safety check: Pass | MIT | |
| Architect Before You Buildjsmastery-pro/jsm-agent-skill | 218 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Iterative Development Orchestratorprime-radiant-inc/iterative-development | 181 | — | ~2.7k | Automated safety check: Pass | Apache-2.0 |
byungjunjang/jangpm-meta-skills
Socratic interview skill to deepen a spec or refine an existing agent blueprint.
pietheinstrengholt/rssmonster
Grill the user relentlessly about a plan, decision, or idea.
meain/dotfiles
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.
jsmastery-pro/jsm-agent-skill
Runs a short design conversation before coding: aligns on terms, works through the decisions that matter and ends with a plan you confirm.
prime-radiant-inc/iterative-development
Runs an autonomous loop that extracts requirements with proof obligations, builds a walking skeleton, then audits sprint by sprint against real behavior evidence.
ayoubben18/ab-method
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.
Archive228/loopkit
Escalate blocked runs to a human via configured channel or fallback to BLOCKED.md and exit the loop.
Archive228/loopkit
Get JSON out of the model reliably. An agent skill from Archive228/loopkit.
Archive228/loopkit
Before compaction Loopkit extracts decisions into claude-decisions.json (machine-readable).
Archive228/loopkit
Build a repeatable eval loop that grades agent output with an LLM judge, so prompt/skill changes get scored against a baseline instead of eyeballed.
Archive228/loopkit
Enumerate every end-to-end feature as strict JSON entries with passes:false, editable-passes-only discipline, and priority order.
Archive228/loopkit
Cache the parts of the prompt that don't change so a long-running loop stops paying full price on every turn.
Categories
A skill your agent uses when starting any conversation in a loopkit-enabled project - establishes how to find and use loopkit's 49 skills, requiring skill invocation before ANY response including…. Using Loopkit is an agent skill from Archive228/loopkit. Use when starting any conversation in a loopkit-enabled project - establishes how to find and use loopkit's 49 skills, requiring skill invocation before ANY response including clarifying questions.
Using Loopkit fits situations like: starting any conversation in a loopkit-enabled project - establishes how to find and use loopkits 49 skills; requiring skill invocation before ANY response including clarifying questions.
Run `npx skills add Archive228/loopkit --skill using-loopkit -a claude-code`. Or copy the skill folder (skills/using-loopkit in Archive228/loopkit) into .claude/skills/using-loopkit in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Archive228/loopkit --skill using-loopkit -a codex`. Or copy the skill folder (skills/using-loopkit in Archive228/loopkit) into .agents/skills/using-loopkit in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Archive228/loopkit --skill using-loopkit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/using-loopkit, .gemini/skills/using-loopkit, .github/skills/using-loopkit and .opencode/skills/using-loopkit in your project.
SKILL.md names no scripts, command-line tools or credentials: Using Loopkit is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
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.
Using Loopkit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Using Loopkit: Deep Dive (byungjunjang/jangpm-meta-skills, 120 stars), Grilling (pietheinstrengholt/rssmonster, 564 stars), Grill With Docs (meain/dotfiles, 285 stars) and Architect Before You Build (jsmastery-pro/jsm-agent-skill, 218 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Archive228 (a GitHub user) maintains it in Archive228/loopkit, which has 755 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on July 14, 2026.
Source: Archive228/loopkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.