Agent skill

Using Loopkit

by Archive228 in Archive228/loopkit

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…

MITAuto-check passedAgent Workflows

Install Using Loopkit

skills CLI
$ npx skills add Archive228/loopkit --skill using-loopkit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Archive228/loopkit using-loopkit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
using-loopkit
GitHub stars
755
Token cost
~1.4k tokens
SKILL.md length
570 words
Files
1
Skills in repo
43
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Starting any conversation in a loopkit-enabled project - establishes how to find and use loopkits 49 skills
  • SKILL.md covers The Rule, Where the skills live, Skill routing (49 skills, 10… and Red Flags — STOP and check for…, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Requiring skill invocation before ANY response including clarifying questions

What it does

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.

When your agent uses it

  • 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

Example prompts

  • “/using-loopkit”

What it can do on your machine

Read from SKILL.md and the folder at commit 5ae033e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    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.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

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.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from Archive228/loopkit at commit 5ae033e, republished under its MIT licence (© Archive228). 570 words, ~1,357 tokens.

Download SKILL.mdSave it as .claude/skills/using-loopkit/SKILL.md (or your agent's skills folder).
name
using-loopkit
description
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

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

The Rule

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.

Where the skills live

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.

Skill routing (49 skills, 10 tracks)

Task shapeFirst skill
"Fix this bug" / test failing / crashsystematic-debugging, then read-the-trace
"It broke between two commits"bisect-regression
"Flaky test"flaky-hunter
"Add a feature" / write anything newspec-first, then write-failing-test-first
"Refactor" / dead code / deep nestingkill-dead-code, simplify, reduce-nesting
About to claim done / commit / open PRadversarial-verify + verification-before-completion + self-eval-bias
Review a diffadversarial-verify, pr-from-diff
Frontend / UI workdesign-system, a11y-pass, loading-empty-error-states
Security touchowasp-review, authz-check, input-validation, secret-scan, dependency-audit
Data / SQL / migrationssql-review, migration-writer, schema-diff
Docs / changelog / READMEchangelog-from-diff, decision-record, readme-audit
Git opsclean-commits, pr-from-diff, rebase-safely, revert-surgical
Test suite gapscoverage-gaps, contract-test
Running out of contextcontext-budget, tool-restraint
Parallel worksubagent-fanout
Starting a fresh project / major featureplanner-spec-expand, then feature-list-json, then init-script-contract
Bootstrapping into an existing multi-session projectprogress-reading-protocol
Entering an implementation sprintsprint-contract
Calibrating a reviewer / evaluatorevaluator-calibration
New Claude/Sonnet/Opus model landedharness-stripping

Full list: ls .claude/skills/.

Red Flags — STOP and check for a skill

ThoughtReality
"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.
Show full SKILL.md (182 more words)Show less

Priority when multiple skills apply

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).

  • "Let's build X" → planner-spec-expand → feature-list-json → sprint-contract → domain skills → adversarial-verify.
  • "Fix bug Y" → systematic-debugging → read-the-trace → fix → verification-before-completion.
  • "Session open in existing project" → progress-reading-protocol → sprint-contract → work.

Skill release convention

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 loaded
  • SKILL.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.

User instructions win

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

Files

Just SKILL.md in skills/using-loopkit of Archive228/loopkit.

Open the folder on GitHubat commit 5ae033e

Compare with similar skills

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.

Using Loopkit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Using Loopkit this skillArchive228/loopkit755—~1.4kAutomated safety check: PassMIT
Deep Divebyungjunjang/jangpm-meta-skills120—~2.5kAutomated safety check: PassNone
Grillingpietheinstrengholt/rssmonster56431 repos~510Automated safety check: PassMIT
Grill With Docsmeain/dotfiles28520 repos~875Automated safety check: PassMIT
Architect Before You Buildjsmastery-pro/jsm-agent-skill218—~1.1kAutomated safety check: PassMIT
Iterative Development Orchestratorprime-radiant-inc/iterative-development181—~2.7kAutomated safety check: PassApache-2.0

Similar skills

  • Deep Dive

    byungjunjang/jangpm-meta-skills

    Socratic interview skill to deepen a spec or refine an existing agent blueprint.

    120 GitHub stars~2.5k tokensUpdated 2 mo ago
    Agent WorkflowsAuto-check passed
  • Grilling

    pietheinstrengholt/rssmonster

    Grill the user relentlessly about a plan, decision, or idea.

    564 GitHub starsUsed in 31 repos~510 tokens
    Agent WorkflowsAuto-check passed
  • Grill With Docs

    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.

    285 GitHub starsUsed in 20 repos~875 tokens
    DevelopmentAuto-check passed
  • Architect Before You Build

    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.

    218 GitHub stars~1.1k tokensUpdated 3 mo ago
    Agent WorkflowsAuto-check passed
  • Iterative Development Orchestrator

    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.

    181 GitHub stars~2.7k tokensUpdated 4 mo ago
    Agent WorkflowsAuto-check passed
  • Grill With Docs

    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.

    192 GitHub stars~2.1k tokensUpdated 8 days ago
    DevelopmentAuto-check passed

More from Archive228/loopkit

All 43 skills in this repo
  • Hitl Escalate

    Archive228/loopkit

    Escalate blocked runs to a human via configured channel or fallback to BLOCKED.md and exit the loop.

    755 GitHub stars~1.2k tokensUpdated 2 mo ago
    Auto-check passed
  • Structured Output

    Archive228/loopkit

    Get JSON out of the model reliably. An agent skill from Archive228/loopkit.

    755 GitHub stars~830 tokensUpdated 2 mo ago
    Auto-check passed
  • Active Memory Reminder

    Archive228/loopkit

    Before compaction Loopkit extracts decisions into claude-decisions.json (machine-readable).

    755 GitHub stars~1.2k tokensUpdated 2 mo ago
    Auto-check passed
  • Eval Harness

    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.

    755 GitHub stars~876 tokensUpdated 2 mo ago
    Auto-check passed
  • Feature List JSON

    Archive228/loopkit

    Enumerate every end-to-end feature as strict JSON entries with passes:false, editable-passes-only discipline, and priority order.

    755 GitHub stars~1.2k tokensUpdated 2 mo ago
    Auto-check passed
  • Prompt Caching

    Archive228/loopkit

    Cache the parts of the prompt that don't change so a long-running loop stops paying full price on every turn.

    755 GitHub stars~735 tokensUpdated 2 mo ago
    Auto-check passed

Questions about Using Loopkit

What does Using Loopkit do?

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.

When should I use Using Loopkit?

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.

How do I install Using Loopkit in Claude Code?

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.

How do I install Using Loopkit in Codex?

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.

Can I use Using Loopkit in Cursor, Gemini CLI or GitHub Copilot?

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.

What does Using Loopkit need to run?

SKILL.md names no scripts, command-line tools or credentials: Using Loopkit is instructions for the agent only.

Does Using Loopkit access the network?

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.

Is Using Loopkit safe to install?

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.

What licence does Using Loopkit use?

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.

How many tokens does Using Loopkit use?

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.

What are the alternatives to Using Loopkit?

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.

Who maintains Using Loopkit?

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.