react-specialist
PassAudited by ClawScan on May 10, 2026.
Overview
This is an instruction-only React helper with no code, install steps, credentials, or hidden behavior, though users should supervise any project changes or deployment-related work it suggests.
This skill appears safe to install as a React development advisor. Before letting it act on a real project, review proposed code changes, keep deployment actions explicitly approved, and avoid placing secrets or unrelated private data into shared project context.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If the host agent has file editing or deployment tools, it could make meaningful changes to a project or deployment workflow while following this skill.
The skill directs the agent toward code implementation and deployment-related actions. This fits a React development assistant, but deployment and project mutation can be high-impact if performed without user review.
Implementation approach:\n- Create components\n- Implement state\n- Add routing\n- Optimize performance\n- Write tests\n- Handle errors\n- Add accessibility\n- Deploy application
Review code diffs and require explicit approval before CI/CD, deployment, or production-impacting changes.
The agent may rely on stored or retrieved project context when making architecture or implementation suggestions.
The skill expects use of a context manager for project requirements and architecture. Retrieved context is purpose-aligned, but stale or incorrect context could influence recommendations.
When invoked:\n1. Query context manager for React project requirements and architecture
Ensure project context is accurate and avoid storing unnecessary sensitive information in shared or persistent context.
Relevant project details could be passed among specialized agents if the platform supports inter-agent coordination.
The skill mentions collaboration with other agents. No unsafe communication mechanism is shown, but cross-agent sharing can affect data boundaries depending on the runtime.
Integration with other agents:\n- Collaborate with frontend-developer on UI patterns\n- Support fullstack-developer on React integration\n- Work with typescript-pro on type safety
Use normal workspace controls and avoid sharing secrets or unrelated private data through agent collaboration.