GitHub repository access in containerized environments using REST API and credential detection. Use when git clone fails, or when accessing private repos/writing files via API.
日本語の概要は準備中です。原文の説明を表示しています。
Break out of a locked problem frame by picking one disciplined move — reframe, provocation (Po), random stimulus, SCAMPER, inversion, structured analogy, constraint play, or family traversal — and committing to it before evaluating. Use when stuck, when options feel narrow or obvious, when iterations produce variations of the same idea, or when the user says "widen this", "break out of", "think differently", "I'm stuck", "feels too obvious", "stress-test the framing", "what am I missing", or holds two related examples and asks what lies between or beyond them. Complements challenging (which evaluates) and convening-experts (which synthesizes viewpoints); this skill generates distance, not judgment.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Fixation is the default state. When a generator (human or LLM) has been working on a problem, attention concentrates on the current framing and subsequent ideas tend to be local variations on it. This skill is the interrupt: spend one move stepping sideways, then resume.
The discipline matters more than the move. Pick ONE technique per invocation, run it without second-guessing, and produce explicit reframings or candidate entry points — not a brainstorm list in the same frame.
Claude activates this skill when:
Do NOT activate this skill as a default before every consequential task — fixation is the trigger, not stakes. If the current frame is working, let it work.
Three rules that apply across every move below. Violations make the output ideation-flavored but structurally identical to what came before.
Stop condition. Stop when the move has produced 3+ non-trivial framings, or a single framing that reorganizes the problem (one sharp surprise beats five adjacent). Do not keep generating because the list looks short — volume is not the product.
The fire test. After every move, ask: could this output have been produced without the move? If yes, the move did not fire. Either commit harder (push the provocation further, make the reframe more aggressive, re-roll the random word, invert on a different axis) or the move was mismatched to the stuck-pattern — re-diagnose and pick the better-matched move. Re-diagnosis after a miss is not menu-rotation; menu-rotation is cycling through techniques without commitment. One move at a time, each one fully, and if it misses, diagnose why before the next.
Tail sift. The fire test with a number attached. Post-trained models carry a typicality bias: asked for one candidate they return the modal one, and asked for a list they return the top-k modes — a bestseller list, not a sample (Zhang et al. 2025). The 3 framings a move produces are subject to this too. So before evaluating, over-generate — 5 to 8 candidates rather than 3 — and write next to each one the probability, 0 to 1, that a generator still inside the old frame would have produced it. Drop everything above the threshold; the remainder is the move's actual output. Start the threshold at 0.3 and lower it if the survivors still read as adjacent. Writing the number is the mechanism, not decoration: prompts that request a distribution with verbalized probabilities recover diversity that prompts for instances or lists do not, quality holds when the candidates are reasoned rather than listed, and lowering the stated threshold moves output further into the tail. The gain scales with model capability; on a small model the sift adds burden without adding distance.
Match the stuck-pattern to the move. When unsure, default to Reframe.
| If the stuck-pattern is… | Reach for… |
|---|---|
| Framing feels forced ("must be X or Y") | Reframe — change the verb, subject, scope, or level |
| Generator keeps returning near-duplicates | Random stimulus — force an unrelated concept into the frame |
| Obvious answer is wrong but you can't see past it | Provocation (Po) — state something impossible, extract movement |
| Iterating on an existing artifact | SCAMPER — seven structured transforms |
| Stuck on "how do we make X succeed?" | Inversion — ask "how do we guarantee X fails?" then negate |
| Problem is defined entirely in one domain's vocabulary | Structured analogy — map objects and relations by function into a distant domain, search there |
| Every solution is blocked by a constraint | Constraint play — remove it ("assume magic"), or add an absurd one ("must fit in a tweet") |
| Two known examples, no theory of the space between/beyond them | Family traversal — name the shared family, walk it to its limits |
The problem-as-stated is rarely the problem-to-solve. Mutate the sentence:
Produce 3 reframings. Fired if: at least one makes the original statement sound naive, or shifts who owns the problem.
Edward de Bono's method. Prefix a deliberately wrong, impossible, or absurd statement with Po: to signal it is not a proposal — it is a stimulus. Then extract movement: what principle, consequence, or adjacent idea does this surface?
Four recipes (de Bono's formal provocations):
The canonical example: a factory pollutes a river. Po: the factory is downstream of itself. Impossible, but it generates: move intake downstream of discharge. Internal incentive to not pollute. Closed-loop water. The provocation is discarded; the movement stays.
Fired if: the provocation is genuinely impossible or absurd (not merely edgy), AND extracting movement yields a principle that survives translation back to the real constraints. If the "provocation" is a thing you could actually do, it's a proposal, not a Po — push it further.
Pick a word, object, or domain with no connection to the problem. Force a connection. The forced-feel is the point — it routes around the habituated pathway.
Template: "How is [problem] like [random]?" then "What does that suggest?"
Sourcing for humans: a random Wikipedia article, a nearby physical object, an Oblique Strategies card, a concept from an unrelated field on the current desk. Commit to the first thing you land on; re-rolling defeats the method.
Sourcing for an LLM agent: an LLM asked directly for a random word does not produce one — the same attention that locked the frame picks a word adjacent to it, and post-training biases the pick toward whatever is typical. Two sources work:
references/stimulus-vocabulary.md holds 128 nouns from distant domains for exactly this; the Oblique Strategies deck works the same way. Measured: the recipe reaches near-PRNG faithfulness on long-reasoning models, and on open-ended generation it beat both an injected PRNG seed and a random-number tool call, because the string can be re-hashed for several local choices and the derivation is on the page. Two failure modes, both measured: a lazy extraction that reads only the first character (LLM-generated strings have strong positional bias — 947 of 1000 QwQ-32B strings opened with "7"), and skipping the written arithmetic, after which reasoning models hallucinate the result. Use the whole string; write the sum. Models under ~8B cannot execute the reduction reliably — hand them an external source.Fired if: the connection is genuinely forced (the first 10 seconds feel wrong), and working through the force produces an angle that was not in your prior search space. If the random word feels "relevant" immediately, you re-rolled, picked from attention, or read one character of the seed — get a new one.
For iterating on an existing artifact. Walk the seven prompts once; do not pick favorites in advance.
Fired if: at least one prompt produced a candidate you would not have reached by asking "what's a better version of this?". If all seven outputs are adjacent polish, the artifact is not the unit of analysis — zoom out and try Reframe.
Solve the inverse problem, then negate the solution. Works because failure modes are often more concrete than success paths.
Fired if: inverting surfaced a concrete risk, mechanism, or incentive the forward framing was hiding. If negating the inverted answer gives you the same thing you already had, the inversion was too symmetric — invert on a different axis (goals → incentives, success → unobservable, user → operator).
Move the problem into a distant domain by its relational structure, not by asking the distant domain a question. "How would biology solve this?" is the cross-domain baseline in Shen, Druckmann & Zou (2026), and it collapses almost as hard as no domain prompt at all: across 150 generations per problem, about 5% of proposed domains were unique, and solution diversity (Vendi score) was 8.3 against 5.8 for the unconstrained baseline. Explicit structure-mapping scored 90–173% higher on solution diversity, produced solutions judged novel 50–69% of the time against 1.6–38% for the baselines, and reached domains further from the problem. The written mapping is what changes the outcome.
Four steps, after Gentner's structure-mapping theory:
Domain menu, when step 2 needs a starting point: natural (biology, ecology, geology), trade (kitchen, ER triage, shipping dock), role (CFO, child, historian, adversary), scale (100x, 1/100x).
Fired if: the mapped domain is one the problem's own literature would not cite, AND step 3 returned a named, existing method — not a metaphor. If the object pairs match by resemblance rather than role, or the "method" is the original problem restated in new nouns, the mapping was surface-level; redo step 2 with a further domain.
Constraints define the solution space. Move them deliberately.
Fired if: a relaxed-constraint solution reveals what you actually value (not just what you'll accept), or an added-constraint solution is sharper than the unconstrained one. If both feel like the same answer with a different budget, the binding constraint is elsewhere — find it.
For when you hold two (or more) related instances and generation keeps orbiting them. The pair is not the object — the parametrized family containing both is. Sub-moves in descending observed yield:
Then sharpen and verify: the traversal's real product is questions precise enough to have derivable answers; the discovery happens in the derivation and a cheap measurement, not in the geometry. (A frontier framing of an addressing scheme implied a capacity law, j² ≤ 2^(significand bits); sixty seconds of numpy confirmed a cliff at exactly N = 4096, closing a four-month-old empirical mystery.) Without this step the move outputs taxonomy, not generation.
Fired if: a limit point or constraint-swap landed outside the prior search space, AND at least one output is a checkable claim. If the output is only a tidy classification of the anchors, the move stalled — push further along the edge or swap the constraint.
Caution: do not equate the interior of the space with novelty. In high dimensions essentially all operation is already extrapolation outside the training hull (Balestriero & LeCun 2021), and mixtures of known points are averages. The generative directions are the limits and the constraint-swaps; the chord is a probe, not a doctrine.
LLM agents exhibit a context-bound analog of functional fixedness: attention concentrates on current framing and generates variations of it. A second mechanism compounds it and does not depend on context: preference data favors familiar text, so post-training sharpens the policy toward the modal continuation for any prompt (Zhang et al. 2025, Theorem D.1) — which is why "give me five alternatives" returns five near-neighbors even in a fresh context. Signals this is happening:
When detected, the fix is the same: pick one move from the diagnostic table, execute it on the agent's own current framing, and explicitly write out the new framing(s) before resuming work. The write-out is essential — a framing that stays implicit in attention gets re-absorbed into the previous frame.
Load these only when the user wants depth on a specific technique.
DIAGNOSE: What kind of stuck?
→ framing forced : REFRAME
→ near-duplicates : RANDOM STIMULUS
→ can't see past obvious: PROVOCATION (Po)
→ iterating an artifact : SCAMPER
→ chasing success : INVERSION
→ one domain vocabulary : STRUCTURED ANALOGY
→ blocked by constraint : CONSTRAINT PLAY
→ two examples, no theory: FAMILY TRAVERSAL
DISCIPLINE:
1. Generation before evaluation
2. One move, committed
3. Output framings, not ideas
TAIL SIFT: over-generate 5-8, tag P(old frame reaches it), drop > 0.3
STOP when: 3+ non-trivial framings produced, or one surprising framing that reorganizes the problem.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
GitHub repository access in containerized environments using REST API and credential detection. Use when git clone fails, or when accessing private repos/writing files via API.
日本語の概要は準備中です。原文の説明を表示しています。
Decide which model, effort level, and cascade shape each subagent gets, and how to keep improvement loops safe (evaluator-as-selector, stop on regression). Routes on measured cost-per-completed-task rather than per-token price, because a tier's token count varies more by task shape than price varies across tiers. Covers per-model effort semantics, the concision lever, cascade preconditions, context handoff, and watching a subagent fan-out live. Use when choosing a subagent's model or effort, when choosing how to escalate a failed attempt, or when asked which model or effort a task should get. Grounded in a 2026-07 calibration, a 2026-08 coding-cost study, a 2026-09 seeded-bug repair battery, a 2026-10 Haiku 5.5 ladder priced per spawn, and a 2026-10 retry-versus-escalation ladder on 295 SWE-bench Verified tasks; Managed Agents API specifics are operational, not calibrated.
日本語の概要は準備中です。原文の説明を表示しています。
Securely manages API credentials for multiple providers (Anthropic Claude, Google Gemini, GitHub). Use when skills need to access stored API keys for external service invocations.
日本語の概要は準備中です。原文の説明を表示しています。
Guidance for asking clarifying questions when user requests are ambiguous, have multiple valid approaches, or require critical decisions. Use when implementation choices exist that could significantly affect outcomes.
日本語の概要は準備中です。原文の説明を表示しています。
Pre-change blast-radius report for a symbol or file. Walks tree-sitting references, augments with a plain-text scan over non-parsed files (configs, plain docs), and clusters affected sites by feature (`_FEATURES.md`) or top-level package. Use when about to refactor, rename, or delete something in a repo you don't own — "what breaks if I change `validateUser`", "who calls this", "is this safe to remove", "where is this used", "blast radius", "impact analysis". This is the CONVERGENT pre-change risk skill — for "what is this repo?" use exploring-codebases; for "where is X?" use searching-codebases.
日本語の概要は準備中です。原文の説明を表示しています。
Read Bluesky/ATProto without depending on Bluesky's AppView — interactions on a user's posts, thread replies, any repo's records, network-wide backlinks across every lexicon, an account's handle and PDS history, which collections are active network-wide, and layer-by-layer outage diagnosis. Use when bsky.app or the AppView is down or slow, when a Bluesky read returns timeouts or 5xx, when asked who liked/replied/quoted/reposted something, when pulling live Bluesky context cheaply, when reading records straight from a PDS, when asked who references a record or account anywhere on the network, whether an account has changed handle or migrated servers, or which lexicons and non-Bluesky apps are active on atproto. Complements browsing-bluesky, which routes everything through the AppView and fails when it does.
日本語の概要は準備中です。原文の説明を表示しています。