AGENT SKILLS · ミッション装備 / lilmgenius

lilmgenius · Agent Skills

出典を確認した実質的な文書を持つ Skill が 49 件あります。カードを開くと原文、パッケージ内容、導入方法を確認できます。

lilmgenius
コミュニティ

re0-decide

Turn material submitted for a decision into a traceable, checkable instrument whose verdict is computed from the decider's own answers, never recommending an outcome.

1時間の導入数
4
GitHub Stars
1463
更新日
11月15日
lilmgenius
コミュニティ

re0-git

Rewrite a finished commit's message into a clean, handoff-ready form in your own log style, place a late commit in time order on a linear history, and take a rejected or duplicate commit out of a range, so git log alone tells the story. User-invoked: run it once you've decided to commit.

1時間の導入数
4
GitHub Stars
1463
更新日
11月15日
lilmgenius
コミュニティ

re0-import

Land handed-over material of any shape (a note, a link, a dump, a correction) in the document of an existing knowledge base that owns it: read the base's own routing documents first, edit in each document's own grammar, hash files before writing, and report what cannot be placed instead of guessing. User-invoked. Not for researching the subject or designing a new structure.

1時間の導入数
4
GitHub Stars
1463
更新日
11月15日
lilmgenius
コミュニティ

re0-loop

Run repeated cycles of build, QA, re0-memo and re0-work while preserving learning and letting code die. Use for long agentic projects where progress must be measured by quality-cleared templates, reusable modules, and eliminated anti-patterns rather than hours spent or features accumulated.

1時間の導入数
4
GitHub Stars
1463
更新日
11月15日
lilmgenius
コミュニティ

re0-memo

Turn a finished, failed, or disappointing work cycle into portable lessons, anti-patterns, quality gates, and next-cycle vocabulary, and measure how far the work stands from its objective. Use after a build, QA pass, demo, user complaint or correction, a request the user had to repeat, a user asking why something was not done, a lesson whose own fix caused a new failure, or an abandoned attempt, and always before a restart from v0, when the useful output is what the next pass must learn rather t

1時間の導入数
4
GitHub Stars
1463
更新日
11月15日
lilmgenius
コミュニティ

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing.

1時間の導入数
4
GitHub Stars
1463
更新日
11月15日
lilmgenius
コミュニティ

re0-plan

Open a paperthin iteration's casebook before re0-loop's first turn, seeded with real content the moment the folder exists, never an empty directory. User-invoked, paperthin-only: assumes the full skill package installed. Run when opening a new build cycle in this repo.

1時間の導入数
4
GitHub Stars
1463
更新日
11月15日
lilmgenius
コミュニティ

re0-readme

Keep a repository's README for the person deciding whether and how to use it, its AGENTS.md (or a CLAUDE.md read through it) for the agent working inside it, and the manifests hosts read first (package.json, plugin and marketplace files, agents/openai.yaml) on the repository's one name: audit them with the bundled script, then move each line to the file whose reader needs it and fix each disagreeing manifest. Use when writing, rewriting or reviewing a README or an AGENTS.md, when an agent-only c

1時間の導入数
4
GitHub Stars
1463
更新日
11月15日
lilmgenius
コミュニティ

re0-release

Walk a pending change in the repository it runs in through that repository's release procedure end to end, then tag and publish once confirmed. User-invoked: run it when you've decided to ship.

1時間の導入数
4
GitHub Stars
1463
更新日
11月15日
lilmgenius
コミュニティ

re0-squash

Republish a GitHub repository as one signed commit: squash its whole history into one commit with the same tree, then delete the remote and recreate it under the same name and settings, because a force push leaves the old commits reachable by hash, in forks and in pull requests. User-invoked, and the deletion cannot be undone.

1時間の導入数
4
GitHub Stars
1463
更新日
11月15日
lilmgenius
コミュニティ

re0-style

Fix code in a named change or file list so it matches the conventions its own repository already keeps: run the project's configured formatter and linter in fix mode through the project's own toolchain, then fix by hand what no tool decides (naming, import order, file layout, error style) toward the dominant pattern in neighbouring files, behavior preserved, and ask with counts where the repository keeps two competing conventions. Use for 'make this match the codebase', formatter or linter setup

1時間の導入数
4
GitHub Stars
1463
更新日
11月15日
lilmgenius
コミュニティ

re0-tutorial

Learn one skill of the suite through three graded levels whose completion rests on the learner's own submission, never on an invocation trace.

1時間の導入数
4
GitHub Stars
1463
更新日
11月15日
lilmgenius
コミュニティ

re0-upgrade

Keep one paperthin install current and loaded once: move an old skills.sh install onto the Claude Code or Codex plugin, clear the session-start notice older releases wired, set up the daily update job where skills.sh stays, and bring that install to the full current catalog, all shown and confirmed first.

1時間の導入数
4
GitHub Stars
1463
更新日
11月15日
lilmgenius
コミュニティ

re0-watch

Watch a long-running agent job for stalls and alert by default, with recovery only as a proposal a human approves.

1時間の導入数
4
GitHub Stars
1463
更新日
11月15日
lilmgenius
コミュニティ

re0-work

Restart a project or artifact from v0 while preserving only proven lessons, contracts, gates, vocabulary, real-surface tests, and negative corpus. Use when the foundation is wrong, accumulated code is misleading progress, or a new pass should learn from the old one without inheriting its accidental architecture.

1時間の導入数
4
GitHub Stars
1463
更新日
11月15日
lilmgenius
コミュニティ

re0-workflow

Read one stated intent into numbered requirements, pick and order the installed skills that serve them, check and show that order, then run the steps the session may run and stop where a person must act. Use when someone states a goal but does not know which skills serve it or in what order, asks which skills to use, or wants a job that needs several skills run end to end. Typing /paperthin lands here.

1時間の導入数
4
GitHub Stars
1463
更新日
11月15日
lilmgenius
コミュニティ

scopechk

Check whether an item falls inside a target's existing scope, as the target's own written sources define it; it never sets or narrows the scope of a piece of work. Use before a skill, script, module, rule, feature, doc section, or file is added to, moved into, promoted into, merged into, or upstreamed to a suite, repository, plugin, package, or document, and when someone asks whether X is in scope for Y, whether X belongs in Y, or which of several homes should own X.

1時間の導入数
4
GitHub Stars
1463
更新日
11月15日
lilmgenius
コミュニティ

shower

Cold-read the artifact you're focused on from a fresh, zero-context sub-session to confirm it stands on its own: a shower-thought reset for accumulated session bias. Use when a long session has worn away your fresh eyes and you can no longer tell whether the artifact in focus is clear to someone with no prior context; before a handoff, publish, or merge; or when you want a clean-room comprehension smoke test. Spawns a separate context-free reviewer; it diagnoses, it does not fix.

1時間の導入数
4
GitHub Stars
1463
更新日
11月15日
lilmgenius
コミュニティ

sip

After you create or change an artifact or skill, taste-test it with our own skills instead of trusting your in-session judgment. Use right after writing or editing anything, before calling it done, committing, or handing it off.

1時間の導入数
4
GitHub Stars
1463
更新日
11月15日
lilmgenius
コミュニティ

ssotize

Audit and consolidate a fact that's scattered across places into one canonical source, after approval, and replace the rest with references. Use when asked to find duplication, check consistency, locate the source of truth, deduplicate, consolidate, unify, or establish SSOT across artifacts or platforms. Starts read-only, reports the map and plan, then mutates only after explicit approval.

1時間の導入数
4
GitHub Stars
1463
更新日
11月15日
lilmgenius
コミュニティ

ssotize-local

Consolidate duplicate files or directories into one canonical home after approval, held as an identity by this machine's filesystem: hardlink, symlink, junction, or bind mount, with bytes, ACLs, owner and mode, named streams, xattrs and kept timestamps preserved. Use when consumers need the same bytes at several paths and textual references cannot serve them, when asked to hardlink, symlink, junction or bind-mount duplicate copies, or to dedupe identical files or trees on disk without breaking t

1時間の導入数
4
GitHub Stars
1463
更新日
11月15日
lilmgenius
コミュニティ

feynman

Press a decision you just made until you can explain it to a skeptic in your own words, or surface the gap where you can't. The Feynman test aimed at a choice: understanding is cheapest to fake the moment after you decide, so a fresh critic presses for what you can't actually explain. Use right after picking an option, especially one an agent laid out without arguing for.

1時間の導入数
1
GitHub Stars
1300
更新日
10月20日
lilmgenius
コミュニティ

prism

Split one artifact — a claim, plan, or file — across 2 to 5 independent lenses, one per genuinely distinct failure mode (correctness, security, readability, cost, adversarial-user), and return their convergence: where they agree, where they disagree, and the single next question that resolves the disagreement. Use when one reviewer isn't enough because the failure modes are heterogeneous, or a claim looks strong to its author and needs cross-lens pressure before it ships.

1時間の導入数
1
GitHub Stars
1300
更新日
10月20日
lilmgenius
コミュニティ

readchk

Verify the model's understanding of a user's instruction before spending non-trivial work. Use when a request is long, bundled, high-stakes, hard to undo, or has ambiguous scope or referents such as this, that, it, the other one, whatever is cleaner, or whichever order makes sense. Restate internally, cross-check against available context, proceed silently when resolved, and surface only a genuine surviving fork.

1時間の導入数
1
GitHub Stars
1300
更新日
10月20日