skills
- Type
- Skill
- Scanned
- Nov 13, 2026
- Version
- b2ed3628695e
- Files read
- 143
This project is a collection of 27 Markdown-based skills that guide an AI agent through B2B and B2C sales planning and execution, from cold outreach and deal qualification to compensation design and hiring. It ships no executable code and shows no malicious intent, with its main risk being router instructions that allow editing the workspace's standing agent-instruction file without confirmation and storing confidential pricing floors in a git-tracked file.
What it can reach
- Files
- Instructs the agent to read repository docs, git history, and user-supplied CRM or transcript files, write or update sales-context.md and persistent memory entries, and optionally patch the project's agent-instruction file.
- Network
- Instructs the agent, when web browsing is available, to search and fetch public web pages such as company sites, job postings, funding announcements, and sales media URLs to verify facts and link freshness.
- Shell commands
- Suggests running dig TXT DNS lookups, when shell access is available, to verify SPF, DKIM, and DMARC records during email deliverability reviews.
- Other
- When host integrations exist, reads connected CRM, sequencer, calendar, or call-recording sources, offers to draft emails or calendar invites with user approval, and proposes or schedules recurring check-in routines.
Findings
-
LowRouter skill permits editing the project's agent-instruction file without confirmation
skills/sales-kickoff/SKILL.md:235
During startup detection, sales-kickoff reads repository files and any connected CRM, call-recording, or meeting-note integrations, and later tells the agent it may optionally patch the project's standing agent-instruction file (such as CLAUDE.md or AGENTS.md) without requiring a diff preview or user approval. Unlike the memory and routine sections in the same file, this step lacks a confirmation gate, allowing unrequested changes to instructions that govern all future sessions—or giving prompt-injected text from untrusted CRM or transcript notes an encouraged persistence target.
Fix: Require showing a diff and getting explicit user approval before modifying any agent-instruction file, and forbid incorporating text from external connectors into standing instructions.
-
LowConfidential pricing floors are written to git-tracked sales-context.md despite memory exclusion
skills/sales-kickoff/SKILL.md:219
Section 6 explicitly forbids saving discount floors and contract pricing into persistent memory—and tells the agent to state this exclusion to the user—yet Section 5 and its template record the user's pricing floor in sales-context.md at the project root to be committed to git without an approval check. In a repository shared with broader staff, contractors, or external collaborators, committing sales-context.md can expose walk-away pricing that the user expected to be kept out of stored state.
Fix: Apply the same sensitive-data exclusion list (omitting pricing and discount floors) and explicit diff-and-approval gate to sales-context.md that Section 6 applies to persistent memory.
-
LowOutbound sequence skill instructs starting recurring background checks without an approval gate
skills/sales-outbound-sequence/SKILL.md:106
Unlike sales-kickoff and sales-radar, which require showing a dry-run or offering before creating scheduled routines, sales-outbound-sequence directly tells the agent to watch stale prospect lists on a recurring schedule whenever the harness supports scheduled checks. In agent environments with background automation enabled, this can register recurring external lookup jobs without explicit user sign-off.
Fix: Change the instruction to propose the recurring trigger check as a dry-run and schedule it only after explicit user approval.
