Agent Ui
Analysis
This is a coherent documentation-only skill for adding an agent UI component, with a few expected setup risks around remote package installation, an API key, and agent-driven UI tools.
Findings (4)
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
npx shadcn@latest add https://ui.inference.sh/r/agent.json npm install @inferencesh/sdk
The setup asks the user to fetch a remote shadcn component and install an npm SDK without pinning versions. This is expected for this UI component workflow, but it depends on upstream package and registry provenance.
system_prompt: 'You can fill forms using scan_ui and fill_field tools.'
The documented client-side tools let an agent inspect UI state and fill form fields in the browser. This matches the stated agent UI purpose and is paired with human-in-the-loop features, but it can affect user-facing forms if enabled broadly.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
INFERENCE_API_KEY=inf_...
The skill requires an inference service API key in the app environment, while the registry metadata declares no required env vars or primary credential. The API key use is expected for the documented proxy route, but users should notice the credential requirement.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
proxyUrl="/api/inference/proxy" ... allowFiles | boolean | Enable file uploads ... allowImages | boolean | Enable image uploads
The component is designed to communicate through an inference proxy and can optionally allow file and image uploads. This is disclosed and purpose-aligned, but it means user content may flow through the configured inference service.
