sales-engineer
PassAudited by ClawScan on May 10, 2026.
Overview
This is an instruction-only sales-engineering persona with no code, install steps, credentials, or declared system access, though it should be used carefully around customer data and high-impact technical actions.
This skill appears safe to install as an instruction-only sales-engineering assistant. Before using it with real customers or production tools, keep prospect data scoped, verify any reported metrics, and require explicit approval for POC changes, data migration, role changes, or penetration testing. The provided SKILL.md content was truncated, so this assessment covers only the supplied artifact text.
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 connected to real tools, the agent could suggest or attempt changes in demo, customer, or integration environments.
These are legitimate sales-engineering and POC activities, but if an agent has access to deployment, customer, or admin tools, environment provisioning and data migration can materially change systems or data.
Proof of concept development:\n- Success criteria definition\n- Environment provisioning\n- Use case implementation\n- Data migration\n- Integration setup
Use this skill for planning and documentation by default; require explicit human approval and a scoped sandbox before provisioning environments, migrating data, changing roles, or running security tests.
Customer requirements, architecture details, or competitive information may be pulled into the agent's working context.
The skill may use stored prospect or customer context. That is consistent with sales engineering, but such context can include sensitive commercial, technical, or security information.
When invoked:\n1. Query context manager for prospect requirements and technical landscape
Ensure the context manager only contains information authorized for this task, and avoid storing secrets, credentials, or confidential customer data unless explicitly intended.
A user or customer could be misled by precise performance claims that were not actually measured for the current engagement.
The fixed completion message contains specific success metrics. If emitted verbatim, it could overstate or fabricate outcomes.
Delivery notification:\n"Sales engineering completed. Delivered 47 technical demonstrations with 82% technical win rate. POC success rate at 78%, reducing average sales cycle by 40%."
Treat this as a template only; replace all metrics with verified values or remove them.