القائمة
Spawn a customized CC subagent with full MCP tool access. Used by SOPs that declare execution: subagent.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/yogsoth-ai/de-anthropocentric-research-engine --skill spawn-agentيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
Strategy: Dialectic engine retuned for truth-seeking, not survival. A defender steelmans a claim into its MOST falsifiable form, a critic attacks to refute it, a judge classifies the exchange into BROKEN/CORROBORATED/UNFALSIFIABLE — the judge does NOT pick a winner or score persuasiveness. Methods: Irving debate (repurposed), Toulmin argumentation, Mayo severe testing.
Campaign: Logical extreme and boundary testing via reductio ad absurdum and edge-case analysis. Core question: Does this artifact collapse under logical limits and boundary conditions? Methods: Lakatos 1976, Dutilh Novaes 2016, BVA, Flyvbjerg Critical Case, Popper.
Campaign for mapping argument structures — extract claims, link evidence, assess strength, synthesize positions. Produces argument graphs in the wiki vault.
| name | spawn-agent |
| description | Spawn a customized CC subagent with full MCP tool access. Used by SOPs that declare execution: subagent. |
| type | sop |
| layer | sop |
When an SOP declares execution: subagent in its frontmatter, this skill governs how main CC creates and invokes that subagent.
| Dimension | Default |
|---|---|
| Model | opus |
| Tools | all (subagent inherits main CC's full MCP access) |
| Output | markdown |
When you encounter an SOP with execution: subagent:
Read the file specified in the SOP's prompt frontmatter field (relative to the SOP directory).
Take the SOP's input parameters and format as:
[FIELD_NAME]:
[value]
[FIELD_NAME]:
[value]
Each field on its own line, separated by blank lines. Field names in UPPER_CASE.
Agent({
description: "[SOP name] — [brief task description]",
prompt: "[prompt.md content]\n\n---\n\n[formatted user message]",
model: "[opus, unless SOP overrides]"
})
The subagent's prompt combines:
---)The Agent tool result IS the SOP output. Pass it back to the calling tactic/strategy as-is. No parsing, no transformation.
If the SOP frontmatter contains override fields:
model: sonnet → use model: "sonnet" in Agent calltools: [alphaxiv, ss] → add tool restriction note to the promptWhen a tactic needs multiple subagents (e.g., debate with Critic + Defender), spawn them as parallel Agent tool calls in a single message. The Agent tool natively supports this.