Freelance Proposal Writer Pro
Analysis
The included code looks like a simple local proposal-template CLI, but the documentation asks for an unspecified API key and directs users to globally install a differently named npm package, so it needs review before installation.
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.
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.
npm install -g freelance-proposal-writer
The documented global npm install points to `freelance-proposal-writer`, while the supplied package metadata names the reviewed package `freelance-proposal-writer-pro`; following the documented install could pull unreviewed external code rather than the artifact under review.
let proposal = template.template; ... proposal = proposal.replace(/{{clientName}}/g, options.clientName || 'Hiring Manager')The implementation shown generates proposals through static template replacement, while the documentation repeatedly markets the skill as AI-powered with Pro subscription features; this mismatch can mislead users about what the tool actually does.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
创建 `~/.freelance-proposal/config.json`: { "apiKey": "your-api-key", ... }The skill asks users to store an unspecified API key in a persistent config file, while the registry metadata declares no required credentials and the supplied code does not define which provider or permission scope the key needs.
