second-opinion
Independent second opinion via a sub-agent. Three modes: Review (diff review with pass/fail), Challenge (adversarial mode that tries to break your code), Consult (ask anything with session continuity). The independent developer who hasn't seen your conversation. Use when: "second opinion", "another perspective", "challenge this", "independent review", "what would someone else think".
Best use case
second-opinion is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Independent second opinion via a sub-agent. Three modes: Review (diff review with pass/fail), Challenge (adversarial mode that tries to break your code), Consult (ask anything with session continuity). The independent developer who hasn't seen your conversation. Use when: "second opinion", "another perspective", "challenge this", "independent review", "what would someone else think".
Teams using second-opinion should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/codex/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How second-opinion Compares
| Feature / Agent | second-opinion | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Independent second opinion via a sub-agent. Three modes: Review (diff review with pass/fail), Challenge (adversarial mode that tries to break your code), Consult (ask anything with session continuity). The independent developer who hasn't seen your conversation. Use when: "second opinion", "another perspective", "challenge this", "independent review", "what would someone else think".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# Second Opinion — Independent AI Review
Spawn a sub-agent with fresh context — no bias from your current conversation. Three modes.
---
## Mode 1: Review
Independent diff review against the base branch.
1. Get the diff: `git diff origin/<base>`
2. Assemble a context block: branch name, diff stat, commit messages, what the PR claims to do
3. Spawn a sub-agent with this prompt:
> You are an independent code reviewer seeing this diff for the first time. No prior context.
>
> Context: {branch}, {N} files changed, {stat summary}
> Commits: {commit messages}
> Stated intent: {what the PR says it does}
>
> Diff:
> {full diff}
>
> Review this diff. Be direct. Name specific files and line numbers.
> 1. What's GOOD about this code?
> 2. What's BROKEN or will break in production?
> 3. What's MISSING (tests, error handling, edge cases)?
> 4. Verdict: PASS / CHANGES REQUESTED / BLOCKED
4. Present the output verbatim under `SECOND OPINION:` header
5. Synthesize: where you agree, where you disagree, whether it changes your verdict
---
## Mode 2: Challenge
Adversarial mode — the sub-agent tries to break your code.
1. Read the changed files fully
2. Spawn a sub-agent:
> You are an adversarial code reviewer. Your job is to BREAK this code.
>
> Changed files:
> {file contents}
>
> For each file:
> 1. Find inputs that crash it
> 2. Find race conditions
> 3. Find security holes
> 4. Find edge cases the author didn't consider
> 5. Find performance traps
>
> Be creative. Be mean. Think like a bug bounty hunter.
> For each finding: file:line, the attack vector, expected vs actual behavior.
3. Present findings. For each confirmed vulnerability, offer to fix it.
---
## Mode 3: Consult
Ask the sub-agent anything about your codebase.
1. Assemble context: relevant files, current problem, what you've tried
2. Spawn a sub-agent:
> Context: {relevant code and problem description}
>
> The user asks: {question}
>
> Be direct. Name specific files and functions. If you're guessing, say so.
> If you need more context, say exactly what you need.
3. Present the answer. If it needs follow-up, loop.
---
## How to Invoke
Ask the user:
> What do you want?
> - **Review** — independent diff review (pass/fail)
> - **Challenge** — adversarial mode, try to break my code
> - **Consult** — ask anything about the codebase
Then proceed with the matching mode.
## Important
- The sub-agent has **no memory of your conversation.** That's the feature — fresh eyes.
- Present its output **verbatim.** Don't summarize or filter.
- After presenting, synthesize: agree/disagree, what changes.
- If the sub-agent fails or times out: "Second opinion unavailable. Continuing without it."Related Skills
second-level-thinking
Apply Howard Marks' Second Level Thinking framework to investment decisions. Use this skill whenever the user is analyzing an investment opportunity, evaluating a trade thesis, stress-testing a conviction, or asking whether a stock/asset/market is actually as attractive as it looks. Also trigger when the user wants to challenge their own reasoning ("am I just following the crowd?"), wants to identify what the market is mispricing, is debating whether a consensus view is already fully reflected in price, or asks about risk/reward asymmetry, market cycles, or contrarian positioning. The skill channels Marks' philosophy: superior returns require being different AND right — and that starts with understanding what everyone already believes.
opinion-analyzer
多视角舆情分析助手。当用户需要分析某个话题/事件/人物/品牌的舆情时使用。 参考 BettaFish 多 Agent 协作机制，从多个视角还原舆情原貌，打破信息茧房，输出结构化分析报告。 触发词：舆情分析、话题分析、品牌声誉、网络讨论、分析XX事件、XX话题怎么看、公众对XX的看法
---
name: article-factory-wechat
humanizer
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
tavily-search
Use Tavily API for real-time web search and content extraction. Use when: user needs real-time web search results, research, or current information from the web. Requires Tavily API key.
baidu-search
Search the web using Baidu AI Search Engine (BDSE). Use for live information, documentation, or research topics.
agent-autonomy-kit
Stop waiting for prompts. Keep working.
Meeting Prep
Never walk into a meeting unprepared again. Your agent researches all attendees before calendar events—pulling LinkedIn profiles, recent company news, mutual connections, and conversation starters. Generates a briefing doc with talking points, icebreakers, and context so you show up informed and confident. Triggered automatically before meetings or on-demand. Configure research depth, advance timing, and output format. Walking into meetings blind is amateur hour—missed connections, generic small talk, zero leverage. Use when setting up meeting intelligence, researching specific attendees, generating pre-meeting briefs, or automating your prep workflow.
self-improvement
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Claude ('No, that's wrong...', 'Actually...'), (3) User requests a capability that doesn't exist, (4) An external API or tool fails, (5) Claude realizes its knowledge is outdated or incorrect, (6) A better approach is discovered for a recurring task. Also review learnings before major tasks.
botlearn-healthcheck
botlearn-healthcheck — BotLearn autonomous health inspector for OpenClaw instances across 5 domains (hardware, config, security, skills, autonomy); triggers on system check, health report, diagnostics, or scheduled heartbeat inspection.
linkedin-cli
A bird-like LinkedIn CLI for searching profiles, checking messages, and summarizing your feed using session cookies.