{
  "skill_name": "geo-content-brief-skill",
  "description": "将 GEO 内容访谈、关键词笔记和渠道约束整理成可执行的中文内容简报 Skill，适用于团队复用、触发边界审查和后续质量评估。",
  "intent_confidence": {
    "score": 10,
    "band": "low",
    "gate_passed": false
  },
  "github_benchmarks": [],
  "source_tracks": [
    {
      "source_type": "official",
      "name": "Official skill anatomy and context discipline",
      "evidence_mode": "curated-pattern-track",
      "matched_keywords": [
        "general fit"
      ],
      "borrow": "Borrow progressive disclosure: keep the entrypoint lean and move depth into references or scripts.",
      "avoid": "Do not let packaging or platform concerns swallow the core job boundary.",
      "why_relevant": "This track matches: general fit."
    },
    {
      "source_type": "research",
      "name": "Hypothesis-test-learn loop",
      "evidence_mode": "curated-pattern-track",
      "matched_keywords": [
        "general fit"
      ],
      "borrow": "Borrow a small hypothesis-test-learn loop so the first revision is evidence-backed.",
      "avoid": "Do not create experimental overhead that exceeds the skill's real risk tier.",
      "why_relevant": "This track matches: general fit."
    },
    {
      "source_type": "principles",
      "name": "Boundary-first design",
      "evidence_mode": "curated-pattern-track",
      "matched_keywords": [
        "general fit"
      ],
      "borrow": "Borrow the discipline of defining what the skill should not own before growing the package.",
      "avoid": "Do not expand execution assets until route boundaries stay clean.",
      "why_relevant": "This track matches: general fit."
    }
  ],
  "synthesis": {
    "borrow_now": [
      "Borrow progressive disclosure: keep the entrypoint lean and move depth into references or scripts.",
      "Borrow a small hypothesis-test-learn loop so the first revision is evidence-backed.",
      "Borrow the discipline of defining what the skill should not own before growing the package."
    ],
    "avoid_now": [
      "Do not let packaging or platform concerns swallow the core job boundary.",
      "Do not create experimental overhead that exceeds the skill's real risk tier.",
      "Do not expand execution assets until route boundaries stay clean."
    ],
    "quality_risers": [
      "Use GitHub repositories for concrete package and workflow patterns.",
      "Use curated official or commercial tracks for entrypoint and operator ergonomics.",
      "Use research tracks to justify the smallest evaluation loop that still catches regressions.",
      "Use principle tracks to keep the package small, boundary-aware, and outcome-driven."
    ],
    "pattern_gate": {
      "threshold": 2,
      "source_count": 3,
      "accepted": [
        {
          "name": "Official skill anatomy and context discipline",
          "source_type": "official",
          "borrow": "Borrow progressive disclosure: keep the entrypoint lean and move depth into references or scripts.",
          "avoid": "Do not let packaging or platform concerns swallow the core job boundary.",
          "gates": {
            "recurrence": true,
            "generativity": true,
            "distinctiveness": false,
            "boundary": true
          },
          "passed": [
            "recurrence",
            "generativity",
            "boundary"
          ],
          "missing": [
            "distinctiveness"
          ],
          "score": 3
        },
        {
          "name": "Hypothesis-test-learn loop",
          "source_type": "research",
          "borrow": "Borrow a small hypothesis-test-learn loop so the first revision is evidence-backed.",
          "avoid": "Do not create experimental overhead that exceeds the skill's real risk tier.",
          "gates": {
            "recurrence": true,
            "generativity": true,
            "distinctiveness": false,
            "boundary": true
          },
          "passed": [
            "recurrence",
            "generativity",
            "boundary"
          ],
          "missing": [
            "distinctiveness"
          ],
          "score": 3
        },
        {
          "name": "Boundary-first design",
          "source_type": "principles",
          "borrow": "Borrow the discipline of defining what the skill should not own before growing the package.",
          "avoid": "Do not expand execution assets until route boundaries stay clean.",
          "gates": {
            "recurrence": true,
            "generativity": true,
            "distinctiveness": false,
            "boundary": true
          },
          "passed": [
            "recurrence",
            "generativity",
            "boundary"
          ],
          "missing": [
            "distinctiveness"
          ],
          "score": 3
        }
      ],
      "deferred": [],
      "summary": "3 accepted, 0 deferred using threshold 2/4."
    },
    "conflicts": [
      {
        "key": "lightweight_vs_governance",
        "summary": "The stated preference leans lightweight or speed-first, while the benchmark mix leans toward governance, review, or heavier evaluation structure.",
        "user_preference": "lightweight or speed-first",
        "benchmark_pressure": "governance or evaluation-heavy patterns"
      }
    ],
    "recommendation": {
      "summary": "Start by borrowing this pattern: Borrow progressive disclosure: keep the entrypoint lean and move depth into references or scripts. Avoid this for the first pass: Do not let packaging or platform concerns swallow the core job boundary.",
      "borrow_now": [
        "Borrow progressive disclosure: keep the entrypoint lean and move depth into references or scripts.",
        "Borrow a small hypothesis-test-learn loop so the first revision is evidence-backed."
      ],
      "avoid_for_now": [
        "Do not let packaging or platform concerns swallow the core job boundary.",
        "Do not create experimental overhead that exceeds the skill's real risk tier."
      ],
      "why": "There is a real design conflict to resolve: The stated preference leans lightweight or speed-first, while the benchmark mix leans toward governance, review, or heavier evaluation structure.",
      "user_decision_required": true
    },
    "visibility": {
      "mode": "explicit",
      "user_decision_required": true,
      "reasons": [
        "intent_uncertain",
        "design_conflict"
      ],
      "user_note": "Surface the recommendation because intent is still settling or there is a real design conflict that needs a user call.",
      "reviewer_note": "Keep the full benchmark and synthesis evidence visible for authors and reviewers."
    },
    "decision_prompt": "Use the recommendation by default. Only surface the underlying benchmark tradeoffs when intent is uncertain or a real design conflict needs a deliberate call.",
    "source_mix": {
      "github_benchmarks": 0,
      "curated_tracks": 3,
      "user_references": 0
    }
  }
}
