AgentSkillsCN

meta-llm-type

根据正确的 LLM 组件类型对功能进行诊断:技能、代理,或命令封装。 适用场景: - “这应该算作技能吗?” - “是命令还是代理?” - “这个功能应该归为哪一类?” - “技能 vs 命令” - “诊断这一功能” - LLM 组件的结构与架构决策 不适用场景: - 实际实现(应使用生成的规范代替) - 与结构设计无关的常规编码任务

SKILL.md
--- frontmatter
name: meta-llm-type
description: |
  Diagnose features into the right LLM component type: Skill, Agent, or Command wrapper.
  
  USE WHEN: 
  - "should this be a skill?"
  - "command or agent?"
  - "what type should this be"
  - "skill vs command"
  - "diagnose this feature"
  - structure/architecture decisions for LLM components
  
  DO NOT USE WHEN:
  - Actually implementing (use the generated spec instead)
  - General coding tasks unrelated to structure design

Structure Organizer

Organize features into the right structure: Command, Skill, or Agent for AI coding assistants.

Quick Reference

Core Types (Knowledge Layer)

ComponentTriggerReasoningExecutionUse When
SkillAuto-load on keywords / direct @pathNoneNo execution (knowledge)Domain expertise to share
AgentGoal assignedLLM decidesDynamic, iterativeMulti-step planning required

Optional Wrapper (Access Layer)

ComponentTriggerPurposeUse When
CommandHuman /commandUI entry point + constraints over Skill/Agentallowed-tools restriction, dangerous ops, structured $ARGUMENTS, frequent shortcut

Key insight: Command is NOT a parallel type to Skill/Agent. It is an access pattern — a UI + security wrapper placed over Skills or Agents when human entry point and platform constraints are needed.

Workflow Routing

IntentWorkflow
Analyze a feature requestworkflows/analyze.md
Generate spec templateworkflows/generate-spec.md

Core Resources

ResourcePurpose
Decision TreePrimary decision logic
Criteria MatrixDetailed comparison criteria
Boundary Cases12 common confusions
Combination PatternsMulti-component architectures
TemplatesSpec templates for each type

Architecture Model

code
Knowledge Layer:  Skill (knowledge)  |  Agent (reasoning)
Access Layer:     Command (optional UI + constraints wrapper)

Common Patterns

PatternStructureUse When
Skill onlyDirect invocation via @path or keywordsMost cases — knowledge is self-sufficient
Agent + SkillsExecutor + KnowledgeAgent needs domain expertise
Command wrapping SkillEntry + Knowledge + ConstraintsTool restriction or frequent human shortcut needed
Command wrapping AgentEntry → ExecutorUser triggers dangerous/complex work
Full StackCommand → Agent → Skills → ToolsCritical ops needing all layers

See combination-patterns.md for details.

Output

This skill outputs:

  1. Diagnosis - Core type (Skill / Agent) + whether Command wrapper is needed
  2. Spec Template - Filled template from references/templates/
  3. Rationale - Why this type, why not others, and why Command wrapper is or isn't needed

Note: This skill diagnoses what type to use. Implementation is handled by the calling Command.

Platform Support

PlatformCommandsSkillsAgents
Claude Code.claude/commands/*.md.claude/skills/*/SKILL.mdSubagent via Task
OpenCode.opencode/commands/*.mdskills/*/SKILL.mdagents/*.md
Cursor.cursor/commands/*.md.cursor/rules/*.mdxAgent mode