design/content-writing/guideline-generation/SKILL.md
This skill generates, creates, or builds brand voice guidelines from source materials. It should be used when the user asks to "generate brand guidelines", "create a style guide", "extract brand voice", "create guidelines from calls", "consolidate brand materials", "analyze my sales calls for brand voice", "build a brand playbook from documents", "synthesize a voice and tone guide", or uploads brand documents, transcripts, or meeting recordings for brand analysis. Also triggers when the user has a discovery report and wants to convert it into actionable guidelines.
npx skillsauth add harsh040506/claude-code-unified-skill-plugin-library guideline-generationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate comprehensive, LLM-ready brand voice guidelines from any combination of sources — brand documents, sales call transcripts, discovery reports, or direct user input. Transform raw materials into structured, enforceable guidelines with confidence scoring and open questions.
Accept any combination of:
When a discovery report is provided, use it as the primary input — sources are already triaged and ranked. Supplement with additional analysis as needed.
Determine what the user has provided. If no sources are available:
/brand-voice:discover-brand run.claude/brand-voice.local.md for known brand material locations/brand-voice:discover-brandFor documents: Delegate to the document-analysis agent for heavy parsing. Extract voice attributes, messaging themes, terminology, tone guidance, and examples.
For transcripts: Delegate to the conversation-analysis agent for pattern recognition. Extract implicit voice attributes, successful language patterns, tone by context, and anti-patterns.
For discovery reports: Extract pre-triaged sources, conflicts, and gaps. Use the ranked sources directly.
Merge all findings into a unified guideline document following the template in references/guideline-template.md. Key sections:
"We Are / We Are Not" Table — The core brand identity anchor:
| We Are | We Are Not | |--------|------------| | [Attribute — e.g., "Confident"] | [Counter — e.g., "Arrogant"] | | [Attribute — e.g., "Approachable"] | [Counter — e.g., "Casual or sloppy"] |
Derive attributes from the most consistent patterns across sources. Each row should have supporting evidence.
Voice Constants vs. Tone Flexes — Clarify what stays fixed and what adapts:
Tone-by-Context Matrix:
| Context | Formality | Energy | Technical Depth | Example | |---------|-----------|--------|-----------------|---------| | Cold outreach | Medium | High | Low | "[example phrase]" | | Enterprise proposal | High | Medium | High | "[example phrase]" | | Social media | Low | High | Low | "[example phrase]" |
Score each section using the methodology in references/confidence-scoring.md:
Generate open questions for any ambiguity that cannot be resolved:
## Open Questions for Team Discussion
### High Priority (blocks guideline completion)
1. **[Question Title]**
- What was found: [conflicting or incomplete info]
- Agent recommendation: [suggested resolution with reasoning]
- Need from you: [specific decision or confirmation needed]
Every open question MUST include an agent recommendation. Turn ambiguity into "confirm or override" — never a dead end.
Before presenting, verify via the quality-assurance agent (defined in agents/quality-assurance.md):
Summarize key findings:
The default save location is .claude/brand-voice-guidelines.md inside the user's working folder.
Important: The agent's working directory may not be the user's project root (especially in Cowork, where plugins run from a plugin cache directory). Always resolve the path relative to the user's working folder, not the current working directory. If no working folder is set, skip the file save and tell the user guidelines will only be available in this conversation.
.claude/brand-voice-guidelines.md inside the user's working folder. Confirm the working folder path before writing.brand-voice-guidelines-YYYY-MM-DD.md in the same directory (using today's date).claude/brand-voice-guidelines.md inside the working folder<full-path>. /brand-voice:enforce-voice will find them automatically in future sessions."The guidelines are also present in this conversation, so /brand-voice:enforce-voice can use them immediately without loading from file.
After saving, offer:
/brand-voice:enforce-voiceEnforce these privacy constraints throughout the entire generation workflow, not only at output time:
references/guideline-template.md — Complete output template with all sections, field definitions, and formatting guidancereferences/confidence-scoring.md — Confidence scoring methodology, thresholds, and examplestesting
Performs quality control on single-cell RNA-seq data (.h5ad or .h5 files) using scverse best practices with MAD-based filtering and comprehensive visualizations. Use when users request QC analysis, filtering low-quality cells, assessing data quality, or following scverse/scanpy best practices for single-cell analysis.
tools
Deep learning for single-cell analysis using scvi-tools. This skill should be used when users need (1) data integration and batch correction with scVI/scANVI, (2) ATAC-seq analysis with PeakVI, (3) CITE-seq multi-modal analysis with totalVI, (4) multiome RNA+ATAC analysis with MultiVI, (5) spatial transcriptomics deconvolution with DestVI, (6) label transfer and reference mapping with scANVI/scArches, (7) RNA velocity with veloVI, or (8) any deep learning-based single-cell method. Triggers include mentions of scVI, scANVI, totalVI, PeakVI, MultiVI, DestVI, veloVI, sysVI, scArches, variational autoencoder, VAE, batch correction, data integration, multi-modal, CITE-seq, multiome, reference mapping, latent space.
testing
This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific decisions. Use this skill when users ask to pitch a new research idea, work through a project problem, evaluate project risks, plan research strategy, navigate decision trees, or get help choosing what scientific problem to work on. Typical requests include "I have an idea for a project", "I'm stuck on my research", "help me evaluate this project", "what should I work on", or "I need strategic advice about my research".
development
Run nf-core bioinformatics pipelines (rnaseq, sarek, atacseq) on sequencing data. Use when analyzing RNA-seq, WGS/WES, or ATAC-seq data—either local FASTQs or public datasets from GEO/SRA. Triggers on nf-core, Nextflow, FASTQ analysis, variant calling, gene expression, differential expression, GEO reanalysis, GSE/GSM/SRR accessions, or samplesheet creation.