psp-kickoff
Find the Next Step in Your PSP Workflow
PSP work can stall when configuration, drafts, vocabulary, and signal sources are at different stages. This skill checks readiness and recommends the next workflow step.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "psp-kickoff" from https://skillstore.io/skills/cmj-hub-psp-kickoff.md and its manifest at https://skillstore.io/api/skills/cmj-hub-psp-kickoff/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "psp-kickoff". Where should I start? My project has no brand configuration.
Expected outcome:
- Brand configuration: missing.
- Recommended next step: onboarding.
- Start by capturing your ideal customer profile and a primary PSP draft.
- Later stages include vocabulary mining, signal-source selection, signal hunting, secondary drafts, and downstream messaging.
Using "psp-kickoff". Show status for a primary PSP refreshed 12 days ago, with eight vocabulary phrases, enabled signal sources, and no secondary draft.
Expected outcome:
- Primary PSP: present and refreshed 12 days ago.
- Vocabulary: eight phrases, meeting the readiness threshold.
- Signal sources: enabled.
- Secondary PSP: not yet built.
- Recommended next step: build a secondary PSP or continue into downstream messaging skills.
Security Audit
SafeAll 19 static findings are false positives: Markdown formatting is not shell execution, and fixed sibling-skill references do not demonstrate unsafe traversal. The file documents local state checks and workflow recommendations. No evidence found of prompt injection, credential access, exfiltration, or destructive operations in the reviewed file.
Risk Factors
โ๏ธ External commands (16)
๐ Filesystem access (3)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/cmj-hub-psp-kickoff/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/cmj-hub-psp-kickoff?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/cmj-hub-psp-kickoff?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cmj-hub-psp-kickoff/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/cmj-hub-psp-kickoff.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
cmj-hub. (2026). psp-kickoff security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cmj-hub-psp-kickoff/audits/1BibTeX citation
@techreport{cmj-hub-cmj-hub-psp-kickoff-2026,
author = {cmj-hub},
title = {psp-kickoff security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/cmj-hub-psp-kickoff/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "psp-kickoff security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "cmj-hub"
date-released: "2026-10-03"
url: "https://skillstore.io/skills/cmj-hub-psp-kickoff/audits/1"
identifiers:
- type: other
value: "skillstore:cmj-hub-psp-kickoff:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Start a New PSP Program
Check missing configuration and identify onboarding as the first step before drafting or signal hunting.
Resume Incomplete PSP Work
Review draft presence, vocabulary readiness, and signal sources to identify the next unfinished stage.
Review Program Freshness
Inspect refresh age and readiness before recommending a secondary PSP or downstream messaging work.
Try These Prompts
Where do I start with PSPs? Check my project state and recommend the first step.
Run /psp status. Summarize configuration, drafts, vocabulary, signal sources, and the recommended next step.
My primary PSP exists. Check vocabulary readiness and signal sources, then recommend the next documented workflow step.
Review my PSP refresh date, secondary draft, and signal sources. Recommend refresh, secondary construction, or downstream work, and identify missing information.
Best Practices
- Keep draft fields, vocabulary, signal-source settings, and refresh dates current before requesting status.
- Use companion skills for onboarding, construction, and signal hunting rather than treating routing as task completion.
- Use real buyer writing for vocabulary and verify readiness before starting downstream outreach.
Avoid
- Treating sample status reports as evidence that project files have been inspected.
- Expecting the kickoff router alone to build drafts, collect signals, or send outreach.
- Assuming missing metadata or an unspecified routing condition means the PSP program is ready.