Agent skill

agent-council

Collect and synthesize opinions from multiple AI agents. Use when users say "summon the council", "ask other AIs", or want multiple AI perspectives on a question.

View SKILL.md on GitHub Repository
Stars 692
Forks 85

Install this agent skill to your Project

npx add-skill https://github.com/team-attention/plugins-for-claude-natives/tree/main/plugins/agent-council

SKILL.md

Agent Council

Collect multiple AI opinions and synthesize one answer.

Usage

Run a job and collect results:

bash
JOB_DIR=$(./skills/agent-council/scripts/council.sh start "your question here")
./skills/agent-council/scripts/council.sh wait "$JOB_DIR"
./skills/agent-council/scripts/council.sh results "$JOB_DIR"
./skills/agent-council/scripts/council.sh clean "$JOB_DIR"

One-shot:

bash
./skills/agent-council/scripts/council.sh "your question here"

References

  • references/overview.md — workflow and background.
  • references/examples.md — usage examples.
  • references/config.md — member configuration.
  • references/requirements.md — dependencies and CLI checks.
  • references/host-ui.md — host UI checklist guidance.
  • references/safety.md — safety notes.

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

team-attention/plugins-for-claude-natives

dev-scan

개발 커뮤니티에서 기술 주제에 대한 다양한 의견 수집. "개발자 반응", "커뮤니티 의견", "developer reactions" 요청에 사용. Reddit, HN, Dev.to, Lobsters 등 종합.

692 85
Explore
team-attention/plugins-for-claude-natives

tech-decision

This skill should be used when the user asks to "기술 의사결정", "뭐 쓸지 고민", "A vs B", "비교 분석", "라이브러리 선택", "아키텍처 결정", "어떤 걸 써야 할지", "트레이드오프", "기술 선택", "구현 방식 고민", or needs deep analysis for technical decisions. Provides systematic multi-source research and synthesized recommendations.

692 85
Explore
team-attention/plugins-for-claude-natives

google-calendar

Google 캘린더 일정 조회/생성/수정/삭제. "오늘 일정", "이번 주 일정", "미팅 추가해줘" 요청에 사용. 여러 계정(work, personal) 통합 조회 지원.

692 85
Explore
team-attention/plugins-for-claude-natives

metamedium

This skill should be used when the user is building, planning, or strategizing and the key question is whether to optimize content (what) or change form (how/medium). Trigger on "내용 vs 형식", "content vs form", "metamedium", "형식을 바꿔볼까", "새로운 포맷", "관점 전환", "perspective shift", "다른 방법 없을까", "같은 방식이 안 먹혀", "diminishing returns". Applies Alan Kay's metamedium concept to surface form-level alternatives. For requirement clarification use vague; for strategy blind spots use unknown.

692 85
Explore
team-attention/plugins-for-claude-natives

unknown

This skill should be used when the user provides a strategy, plan, or decision document and wants to surface hidden assumptions and blind spots using the Known/Unknown 4-quadrant framework. Trigger on "known unknown", "4분면 분석", "blind spots", "뭘 놓치고 있지", "뭘 모르는지 모르겠어", "전략 점검", "전략 분석", "assumption check", "가정 점검", "quadrant analysis", "what am I missing". Strategy-level blind spot analysis with hypothesis-driven questioning. For requirement clarification use vague; for content-vs-form reframing use metamedium.

692 85
Explore
team-attention/plugins-for-claude-natives

vague

This skill should be used when the user's request or requirement is ambiguous and needs iterative questioning to become actionable. Trigger on "clarify requirements", "refine requirements", "요구사항 명확히", "요구사항 정리", "뭘 원하는 건지", "make this clearer", "spec this out", "scope this", "/clarify". Turns vague inputs into concrete specs. For strategy blind spots use unknown; for content-vs-form reframing use metamedium.

692 85
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results