integration-intake
Gate for deciding whether to adopt an external pattern (skill/agent/rule/plugin/MCP/prompt) into your system. Triggers: '/integration-intake [name]', 'should I integrate this', 'is this worth adopting', or sharing a GitHub repo link and asking what to do with it.
AlexZio00 · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add AlexZio00/sovereign-skills --skill integration-intake技能说明
name: integration-intake description: "Gate for deciding whether to adopt an external pattern (skill/agent/rule/plugin/MCP/prompt) into your system. Triggers: '/integration-intake [name]', 'should I integrate this', 'is this worth adopting', or sharing a GitHub repo link and asking what to do with it." user_invocable: true tools: Read, Glob, Grep, WebFetch, WebSearch depends_on: skills: [] agents: [] files: - ~/.claude/skills/ - ~/.claude/agents/ - ~/.claude/rules/ - SKILLS_INVENTORY.md concurrency_profile: read_only: true concurrency_safe: true destructive: none state_footprint: stateless not_for:
- "A decision that's already been made (re-litigating a done deal) -> proceed directly, no gate needed"
- "A 1-2 minute trivial application, where the gate costs more than the decision -> just apply it"
- "A pure internal code change with zero external dependency (not an external-pattern adoption) -> normal implementation flow" see_also: []
/integration-intake — External Pattern Adoption Gate
Dominant Variable
The single variable this gate swings on: does this external pattern add real value to the system, or is what you already have already enough? Get this wrong and your library fills up with redundant patterns, cognitive load goes up, and stale entries pile up.
Trigger
/integration-intake [pattern name]- "should I integrate this", "is this worth adopting"
- "should I bring in this [skill/agent/MCP/rule/pattern]", "is this worth adopting"
- After spotting a pattern in an external repo (GitHub/blog/another system) that looks applicable
- A bare GitHub repo URL shared with an implicit ask to evaluate it — run this gate properly instead of an ad-hoc two-axis (compatibility + philosophy) skim; an ad-hoc skim skips the redundancy check (reject if M/N ≥ 90% covered already) and the provenance gate (malicious body/constraint-text/MCP-config check) this skill provides
- After being shown a new tool/library/prompt with an implicit "how should I use this" ask
Discard If
- Already decided ("we already decided to do this") — re-litigating adds no value
- A trivial 1-2 minute application — the gate costs more than the decision
- Zero external dependency, purely internal code change — not an external-pattern adoption at all
Key Assumptions
- You can Glob/Grep your existing skill/agent/rule inventory — if not, the redundancy check (Phase 1 item 5) can't run and the verdict is invalid.
- The external pattern's source (URL/repo) is stated — if not, provenance can't be verified → REVISE.
Workflow
Phase 0.5: Establish Grounding (mandatory, before Phase 1)
Fires: always.
Why: screening from a summary page alone (a blog writeup, a single WebFetch summary) means you're screening marketing copy, not the actual implementation. A README says "what it claims to do"; the actual code says "what it actually does." These can differ.
- Read the actual README/docs — don't stop at one WebFetch summary. For a GitHub repo, at minimum:
- Actual file/directory structure
- Read the 1-2 core source files implementing the feature the README describes
- Recent commit/issue activity (a stale project affects how much you should trust it)
- For papers/blog posts: don't judge from the abstract/conclusion alone. Confirm the core claim's evidence (experiments/code/data) actually exists in the body.
- No exception for an early REJECT — even an obvious-looking rejection (e.g. wrong structural fit) still needs this step, because filling in the design-philosophy field (Phase 1.7) requires real grounding.
If skipped: mark the report ⚠️ Phase 0.5 not run — judged from a summary only. The verdict still stands but is flagged low-confidence.
Phase 1: 5-Item Screening (mandatory, fixed order)
Any item you can't clearly answer → hold — mark it "not ready."
1. Specificity
Can you state the pattern to extract in one clear sentence?
- ❌ Fails: "looks good overall", "adopt the whole structure"
- ✅ Passes: "Routing Scenarios — validate positive/negative keyword-matching pairs dynamically"
If it fails: ask the user once for clarification. Still vague → hold.
2. Value
What real value does this add for the user? One sentence.
- ❌ "seems nice to have", "it's trendy"
- ✅ "dynamically validates that keyword mappings actually trigger — complements the static routing table"
Fails: reject. "Interesting" is not value.
Triple-check effectiveness claims: an external claim that "this pattern works" (from a README, blog post, or report) should only be trusted as verified when three conditions hold — (a) injecting the pattern shows measurable improvement, (b) removing it shows measurable degradation, and (c) a placebo control (a mechanism-free instruction of similar shape/length) does not produce the same effect. Without this three-way check, treat the effectiveness claim as unverified — a marketing claim, not a fact.
Analogy trap check: a value claim of the form "X does it this way, so should we" needs three answers before it counts — what problem was X actually solving? Is our problem identical along every dimension that matters? What constraints do X and we hold differently? If you can't answer all three, the value claim is riding on analogy alone — treat it as insufficient (reject or ask a follow-up question).
3. Structural Fit
Does it conflict with your existing layered rules, hard rules, or operating conventions?
- Conflict examples: "a custom format outside your standard schema", "weakens an existing safety principle", "bypasses a default-deny rule"
- Fits → go to item 4
- Conflicts → reject, or negotiate a resolution path
4. Global Applicability Check — avoid over-fitting to your current project
Does this pattern hold value for project types other than the one you're currently working on?
- ✅ "applies to any Claude Code project" → design it as a global asset
- ⚠️ "only va