How do I install the Claude skill?

Run npx skillmds@latest add softnanolab/claude in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Claude safe to use?

SkillMD's automated safety review verdict for this skill is CAUTION. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Claude?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Claude free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Claude?

softnanolab (@softnanolab) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Claude by softnanolab — Agent Skill

Name: Claude
Rating: 4.2 (5 reviews)
Author: softnanolab

File contents

Claude Second Opinion

Delegate a task to Claude Code for an independent review or second opinion.

Input

If no task is provided, ask the user what they want Claude to review.

How to Use

Run Claude in non-interactive print mode from the current working directory. Prefer a read-only tool set:

claude -p \
  --permission-mode dontAsk \
  --allowedTools Read,Grep,Glob,LS \
  --add-dir "<current working directory>" \
  "<prompt>"

If the Claude CLI is not installed or is not authenticated, report that blocker and include the command output.

Prompt Construction

Build a self-contained prompt for Claude that includes:

Context: The repo path, what project this is, and what folder/files are relevant
The task: What you want Claude to do (review, validate, suggest, etc.)
Constraints: Tell it to only read files, not modify anything

Keep it unbiased. Do not include your own conclusions or preferred answer. Present the problem neutrally so Claude forms its own opinion.

Be specific about files. Tell Claude exactly which files to read — it has access to the repo but needs direction.

Example

claude -p \
  --permission-mode dontAsk \
  --allowedTools Read,Grep,Glob,LS \
  --add-dir "/path/to/project" \
  "Review the file at src/config.py. Is the retry logic correct? Read the file and give your assessment. Do NOT modify any files."

Troubleshooting

Authentication: If Claude exits with an auth error, ask the user to run claude auth or configure the required Claude credentials before retrying.
Tool restrictions: If Claude cannot read the requested files, retry with a narrower prompt and the same read-only tools. Do not remove read-only restrictions unless the user explicitly approves.
Output truncation: Claude may produce a long review. Keep prompts focused and ask specific questions rather than open-ended reviews.
Session state: Use -p for a fresh non-interactive answer. Do not use --continue or --resume unless the user specifically asks to continue an existing Claude session.

After Claude Responds

Report the Claude response to the user
Note where you agree or disagree with Claude's assessment
Let the user decide how to proceed

---name: claudedescription: Get a second opinion from Claude Code. Use from Codex when you want to cross-check your reasoning, validate a plan, or get an independent review from Claude.---# Claude Second OpinionDelegate a task to Claude Code for an independent review or second opinion.## Input<task>$ARGUMENTS</task>If no task is provided, ask the user what they want Claude to review.## How to UseRun Claude in non-interactive print mode from the current working directory. Prefer a read-only tool set:```bashclaude -p \ --permission-mode dontAsk \ --allowedTools Read,Grep,Glob,LS \ --add-dir "<current working directory>" \ "<prompt>"```If the Claude CLI is not installed or is not authenticated, report that blocker and include the command output.## Prompt ConstructionBuild a self-contained prompt for Claude that includes:1. **Context**: The repo path, what project this is, and what folder/files are relevant2. **The task**: What you want Claude to do (review, validate, suggest, etc.)3. **Constraints**: Tell it to only read files, not modify anything**Keep it unbiased.** Do not include your own conclusions or preferred answer. Present the problem neutrally so Claude forms its own opinion.**Be specific about files.** Tell Claude exactly which files to read — it has access to the repo but needs direction.## Example```bashclaude -p \ --permission-mode dontAsk \ --allowedTools Read,Grep,Glob,LS \ --add-dir "/path/to/project" \ "Review the file at src/config.py. Is the retry logic correct? Read the file and give your assessment. Do NOT modify any files."```## Troubleshooting- **Authentication**: If Claude exits with an auth error, ask the user to run `claude auth` or configure the required Claude credentials before retrying.- **Tool restrictions**: If Claude cannot read the requested files, retry with a narrower prompt and the same read-only tools. Do not remove read-only restrictions unless the user explicitly approves.- **Output truncation**: Claude may produce a long review. Keep prompts focused and ask specific questions rather than open-ended reviews.- **Session state**: Use `-p` for a fresh non-interactive answer. Do not use `--continue` or `--resume` unless the user specifically asks to continue an existing Claude session.## After Claude Responds1. Report the Claude response to the user2. Note where you agree or disagree with Claude's assessment3. Let the user decide how to proceed

Frequently asked questions

Claude