Agent Skills: consensus-voting
Multi-agent consensus voting with domain-weighted expertise for critical decisions requiring structured validation
ID: rysweet/amplihack/consensus-voting
Install this agent skill to your local
Skill Files
The files that make up consensus-voting.
Loading file tree…
More agent skills
- paper-select-journal当用户明确要求“推荐投稿期刊”“帮我的论文选 SCI 杂志”“这篇 manuscript 适合投哪些 journal”“期刊匹配/选刊/投稿建议”时必须使用。适用于用户提供全文、摘要、Markdown、LaTeX、PDF、Word 或混合材料的场景；本 skill 会基于 manuscript 与用户偏好，先用内置 `2023IF.xlsx` 做最小硬过滤生成候选池，再由宿主模型自主规划 Set1/Set2/Set3，并联网核验 scope / 质量 / 近 3 个月 PubMed 论文，最后输出 1 份按推荐度排序的 Markdown 选刊报告。⚠️ 不适用：用户只是想润色论文、只想翻译摘要、或只问某个单一期刊的官网信息而不需要系统选刊。
- ai-persona-creatorUse when analyzing stakeholder psychology for negotiations, proposals, or persuasion. Creates research-backed personas revealing hidden motivations.
- frontend-patternsFrontend development patterns for React, Next.js, state management, performance optimization, and UI best practices. Use when building or reviewing React or Next.js components, state, or render performance.
- acquiring-skillsDiscover and install skills from Hermes, ClawHub, GitHub, and other registries. Load this skill whenever a user asks for a capability you don't already have — image generation, social media, email, calendar, finance, DevOps, search, browser automation, etc.
- repomixPackage entire code repositories into single AI-friendly files using Repomix. Capabilities include pack codebases with customizable include/exclude patterns, generate multiple output formats (XML, Markdown, plain text), preserve file structure and context, optimize for AI consumption with token counting, filter by file types and directories, add custom headers and summaries. Use when packaging codebases for AI analysis, creating repository snapshots for LLM context, analyzing third-party libraries, preparing for security audits, generating documentation context, or evaluating unfamiliar codebases.
- pragmatic-programmerApply meta-principles of software craftsmanship: DRY, orthogonality, tracer bullets, and design by contract. Use when the user mentions "best practices", "pragmatic approach", "broken windows", "tracer bullet", "software craftsmanship", "avoid technical debt", "code ownership", or "how do I become a better developer". Also trigger when evaluating build-vs-buy decisions, designing estimation approaches, or choosing between reversible and irreversible architectural decisions. Covers estimation, domain languages, and reversibility. For code-level quality, see clean-code. For refactoring techniques, see refactoring-patterns.