lucasilverentand/customer-profile
plugins/project-docs/skills/customer-profile/SKILL.md
Writes customer profile and market documents from the project-docs template. Use when the user asks for a customer profile, wants persona or market notes, needs audience assumptions for a project, or is filling customer-profile.md.
$ install --global
skillsauthnpx skillsauth add lucasilverentand/skills customer-profileInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 21, 2026, 7:15 AM148.8s2 files scanned
SKILL.md
- name:
- customer-profile
- description:
- Writes customer profile and market documents from the project-docs template. Use when the user asks for a customer profile, wants persona or market notes, needs audience assumptions for a project, or is filling customer-profile.md.
Customer Profile
Use this skill to capture audience truth for a project so briefs and feature specs can link to it instead of re-describing users and market assumptions.
Decision tree
- What is the user asking for?
- A new customer profile -> read
../../README.mdandreferences/template.md, then draft the profile in the requested destination. - A project brief audience section -> keep the brief short and link to the customer profile for detailed audience, alternatives, and assumption risks.
- Feature-specific user stories -> use the
feature-specskill and reference this profile for audience context. - Research evidence or source trail -> use the
research-briefskill and link it from the customer profile where claims depend on evidence. - Something else -> ask whether the user needs durable audience context or a narrower feature behavior doc.
- A new customer profile -> read
Workflow
- Read
../../README.mdfor shared conventions and relationship rules. - Read
references/template.mdbefore drafting or editing. - Gather who the project serves, what they are trying to do, current alternatives, value drivers, market shape, risks, and unknowns.
- Separate evidence from assumption. Mark unverified claims as assumptions or open questions.
- Avoid collecting personal data unless the project genuinely needs it and the user approved that scope.
- Link to research briefs for evidence trails instead of embedding long source summaries.
Document contract
- When to write: Once there is a rough sense of who the project is for.
- How many: One living document per project.
- Owns: Audience segments, use contexts, alternatives, value, market notes, assumption risks, and open questions.
- Link instead of duplicating: Project justification belongs in the project brief; feature behavior belongs in feature specs; evidence trails belong in research briefs.
Related Skills
lucasilverentand/open-source-docs
tools
VerifiedTrustedCommunity
Creates, audits, and updates public open-source repository documentation, including README files, CONTRIBUTING guides, SECURITY and SUPPORT docs, project badges, quickstarts, usage guidance, community links, and contributor onboarding. Use when maintaining docs for public GitHub projects, libraries, CLIs, apps, or reusable packages, especially when the user says "update this README", "write CONTRIBUTING.md", "make these docs open-source ready", or "improve the public project docs".
3SKILL.mdUpdated Jun 5, 2026
lucasilverentand/closed-source-docs
development
VerifiedTrustedCommunity
Creates, audits, and updates private or closed-source project documentation, including internal README hubs, codebase navigation guides, ownership links, Linear initiative links, onboarding notes, runbooks, and contribution guidance for teams. Use when maintaining docs for private repositories, internal apps, services, infrastructure, or company projects, especially when the user says "make this README an internal hub", "document how to navigate this repo", "add Linear links to the docs", or "write private project documentation".
3SKILL.mdUpdated Jun 5, 2026
lucasilverentand/linear-issues
development
VerifiedTrustedCommunity
Creates, updates, estimates, and tidies Linear issues using Luca's issue-shaping rules. Use when the user asks to create a Linear issue, write ticket-ready issue text, refine an existing issue, add acceptance criteria, set issue relationships, estimate points, audit issue hygiene, tidy a Linear project, find duplicates, fix stale blockers, or normalize labels, milestones, priorities, and issue state.
3SKILL.mdUpdated Jun 5, 2026
lucasilverentand/tidy-linear-project
testing
VerifiedTrustedCommunity
Keeps an existing Linear project tidy after planning and during execution. Use when the user asks to "tidy Linear", "clean up the project", "audit issues", "find duplicates", "check stale blockers", "fix project drift", or run periodic Linear housekeeping on a project, initiative, or milestone set. Use when planning is underway or execution has started and relationships, labels, priorities, documents, and issue states need coherence without changing product scope.
3SKILL.mdUpdated May 29, 2026