원클릭으로 Manus에서 모든 스킬 실행

forge-the-local-circle

스타0

포크0

업데이트2026년 7월 2일 09:08

Use SkDD to forge project-specialized adaptations of the Growth Circle skills — local skills that carry this product's keystone, event names, query paths, contexts, and cadence baked in, so future sessions (and cheaper models) run the circle without rediscovering it. Use when the generic pack has run against a project a few times and keeps re-deriving the same context, when handing growth work to scheduled or lighter-weight agents, or when a project's circle has stabilized enough to be worth freezing as skills.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

zakelfassi

zakelfassi/skdd-commons

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Forge the Local Circle

Freeze what the generic pack learned about this product into project-local skills — a fine-tune by forging, not by weights.

Gate

Requires gate: keystone = open and at least one completed cycle of real work in the ledgers (an experiment run, lore tested, or instrumentation verified). Forging locals from an empty circle just bakes in guesses — there must be something learned before it's worth freezing.

The one hard rule

Local adaptations may specialize prompts, embed data, shortcut discovery, and drop irrelevant branches. They may never weaken the refusals: the gate checks, the virality gate, the alienation test, the consent non-delegables, and the evidence-or-hypothesis rule survive verbatim in every derivative. The refusals are the product; everything else is packaging.

Inputs

GROWTH.md (the learned circle), the generic pack's skills as base templates, and the SkDD skillforge contract (<name>/SKILL.md, YAML frontmatter, forged-* provenance).

Steps

Pick what's worth freezing. Candidates, by payoff: the loop (run-loop-<project> — cadence, experiment scaffolding, where flags and queries live), instrumentation checks (verify-<project>-events — exact event names, first-light procedure), the AEO probe suite (probe-<project>-channel — the intents, the assistants, the log format), context playbooks (grow-<project>-in-<context>). Skip what ran once; freeze what ran three times the same way.
Forge from the base, embedding the local truth. Start from the generic skill's structure; replace discovery steps with the discovered facts (keystone spelled out, queries inline or pathed, stack named). Keep each forged skill ≤200 lines and self-contained — a future agent with only this file and the repo should be able to act.
Carry provenance. Frontmatter on every local: forged-from: <generic-skill> @ 2026-07-growth-circle + GROWTH.md @ <commit> and a one-line forged-reason. The lineage is what makes later upstreaming possible.
Wire and register. Locals live in the project's colony (skills/), registered per SkDD convention; list them in GROWTH.md ## Team as operators, with their lanes and the human veto unchanged. If wind-the-clock runs, point the scheduled jobs at the forged locals — that's the intended pairing: the clock fires, the local skill knows exactly what to do.
Evolve in both directions. When a local hits an edge case: project-specific fixes stay local; generalizable lessons get translated back to the generic skill and pushed upstream to the commons (skdd push) with the edge case attached. When the keystone sunsets or a re-derivation lands, re-forge the affected locals — stale locals are lore in skill form.

Conventions

Locals are named for the project and the job, not the ring — run-loop-acme, not acme-ring-3.
A forged local that only restates the generic skill is noise; if nothing project-specific got embedded, don't forge it.
Cheaper-model handoff is a first-class goal: write locals so a lighter agent can follow them mechanically — the judgment was spent at forge time.

Edge Cases

The project's circle changes under the locals (new keystone, new stack). The re-forge in step 5 is mandatory, not hygienic — run it before the next scheduled job fires with stale facts.
Temptation to fork the refusals ("our team is fine with viral mechanics early"). Refuse, citing the hard rule; if the team overrules, the derivative must drop the Growth Circle lineage from its provenance — it is no longer an adaptation of this pack.
Secrets in the local truth (query credentials, internal URLs). Locals embed paths and names, never credentials; skills travel, and the colony is not a vault.
No SkDD in the environment. The forge still works — a local skill is just a directory with a SKILL.md; register it in whatever the harness uses for skills and note the missing provenance tooling.

이 저장소의 다른 Skills

같은 저장소

name-the-aha

zakelfassi/skdd-commons

Interrogate a product for its core value — name the observable aha moment, measure time-to-aha, or honestly conclude there is none yet. Use when starting Growth Circle work on any repo, when someone asks "how do we grow this", when GROWTH.md is missing or its Aha section is empty, or before any activation/retention/distribution work is proposed. This is the gatekeeper skill — every other growth skill depends on its output.

2026-07-020

prove-the-value

zakelfassi/skdd-commons

Compile a product's earned, evidence-backed claims from GROWTH.md into a public VALUE.md — the proof-of-value surface that agent-mediated discovery reads — with attestation levels, expiry dates, and honest retractions. Use when creating or refreshing a VALUE.md, when marketing copy needs grounding in evidence, when preparing a product to be evaluated by assistants and their principals' agents, or when a published claim has gone stale.

2026-07-020

run-the-loop

zakelfassi/skdd-commons

Run the growth experiment cadence — propose ranked by keystone impact, pre-register before launch, evaluate by the committed rule, keep/kill without relitigating, log everything. Enforces the virality gate (get-users-to-get-users proposals are parked until activation and retention run green) and the alienation test (auto-kill anything a fully-informed user would resent). Use when the growth cadence comes due (weekly/biweekly), when someone proposes "a growth hack", or when experiment results need an honest verdict.

2026-07-020

wind-the-clock

zakelfassi/skdd-commons

Make the growth circle self-running — schedule its recurring checks (loop cadence, keystone sunset, first-light freshness, AEO probes, trust-ledger review) using whatever scheduling primitive the current harness offers, and record every schedule in GROWTH.md so it survives harness changes. Use when the circle's gates are open but nothing recurs, when a keystone sunset or instrumentation check exists only as a date nobody watches, after run-the-loop establishes a cadence, or when growth work keeps happening "whenever someone remembers".

2026-07-020

hire-the-circle

zakelfassi/skdd-commons

Turn growth-team values into working artifacts — role scorecards, interview kits with listen-fors — and map which rings of the growth circle run on agents versus humans, with explicit approval boundaries. Use when hiring a first growth person, when staffing growth work across a human/agent team, when a growth hire is failing and nobody can say why, or when deciding what an autonomous agent may and may not do to users.

2026-07-020

reset-for-context

zakelfassi/skdd-commons

Detect when a playbook that works in one context is failing in another — market, language, platform, segment, or agent-mediated channel — and run the 99/1 reset protocol with native-informed deviations. Use when the same keystone reads very differently across segments, when entering a new market or platform, when metrics are flat somewhere the product "should" work, or when deciding how the product shows up in assistant recommendations.

2026-07-020

name	forge-the-local-circle
description	Use SkDD to forge project-specialized adaptations of the Growth Circle skills — local skills that carry this product's keystone, event names, query paths, contexts, and cadence baked in, so future sessions (and cheaper models) run the circle without rediscovering it. Use when the generic pack has run against a project a few times and keeps re-deriving the same context, when handing growth work to scheduled or lighter-weight agents, or when a project's circle has stabilized enough to be worth freezing as skills.
metadata	{"pack":"2026-07-growth-circle","forged-by":"claude-fable-5","forged-from":"session-2026-07-02-growth-circle — the Growth Circle protocol (github.com/zakelfassi/growth-circle)","forged-reason":"A generic skill spends half its run rediscovering the project; a forged local skill starts already knowing the keystone, the stack, and the queries. SkDD's forge-then-evolve loop is the fine-tune mechanism the pack was designed for — with one hard rule: derivatives may specialize everything except the refusals.","usage-count":"0"}

Forge the Local Circle

Freeze what the generic pack learned about this product into project-local skills — a fine-tune by forging, not by weights.

Gate

The one hard rule

Inputs

GROWTH.md (the learned circle), the generic pack's skills as base templates, and the SkDD skillforge contract (<name>/SKILL.md, YAML frontmatter, forged-* provenance).

Steps

Pick what's worth freezing. Candidates, by payoff: the loop (run-loop-<project> — cadence, experiment scaffolding, where flags and queries live), instrumentation checks (verify-<project>-events — exact event names, first-light procedure), the AEO probe suite (probe-<project>-channel — the intents, the assistants, the log format), context playbooks (grow-<project>-in-<context>). Skip what ran once; freeze what ran three times the same way.
Forge from the base, embedding the local truth. Start from the generic skill's structure; replace discovery steps with the discovered facts (keystone spelled out, queries inline or pathed, stack named). Keep each forged skill ≤200 lines and self-contained — a future agent with only this file and the repo should be able to act.
Carry provenance. Frontmatter on every local: forged-from: <generic-skill> @ 2026-07-growth-circle + GROWTH.md @ <commit> and a one-line forged-reason. The lineage is what makes later upstreaming possible.
Wire and register. Locals live in the project's colony (skills/), registered per SkDD convention; list them in GROWTH.md ## Team as operators, with their lanes and the human veto unchanged. If wind-the-clock runs, point the scheduled jobs at the forged locals — that's the intended pairing: the clock fires, the local skill knows exactly what to do.
Evolve in both directions. When a local hits an edge case: project-specific fixes stay local; generalizable lessons get translated back to the generic skill and pushed upstream to the commons (skdd push) with the edge case attached. When the keystone sunsets or a re-derivation lands, re-forge the affected locals — stale locals are lore in skill form.

Conventions

Locals are named for the project and the job, not the ring — run-loop-acme, not acme-ring-3.
A forged local that only restates the generic skill is noise; if nothing project-specific got embedded, don't forge it.
Cheaper-model handoff is a first-class goal: write locals so a lighter agent can follow them mechanically — the judgment was spent at forge time.

Edge Cases

The project's circle changes under the locals (new keystone, new stack). The re-forge in step 5 is mandatory, not hygienic — run it before the next scheduled job fires with stale facts.
Temptation to fork the refusals ("our team is fine with viral mechanics early"). Refuse, citing the hard rule; if the team overrules, the derivative must drop the Growth Circle lineage from its provenance — it is no longer an adaptation of this pack.
Secrets in the local truth (query credentials, internal URLs). Locals embed paths and names, never credentials; skills travel, and the colony is not a vault.
No SkDD in the environment. The forge still works — a local skill is just a directory with a SKILL.md; register it in whatever the harness uses for skills and note the missing provenance tooling.