persona-intel

I've been looking at how you're handling persona inference here—the approach of breaking down user context into structured attributes is solid, but I'm curious about the edge cases where persona signals conflict or are ambiguous.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 79/100, which is solid C territory—good fundamentals with some gaps that are totally fixable. This is based on Anthropic's skill grading standards across five pillars. Your strongest area is Ease of Use (21/25)—the framework structure is intuitive. Weakest is Spec Compliance (11/15), mainly because your description is missing trigger phrases that help with discoverability.

What's Working Well

• Framework structure is clean. The 5-step approach (Identify → Research → Prioritize → Document → Brief) gives users a clear path without overwhelming them.
• Practical triggers defined. You've nailed the "When to Use" section with specific scenarios like "multi-persona discovery calls" and "exec briefing prep"—that's exactly what users need to know when to reach for this skill.
• Consistent terminology. "Persona," "discovery," "call brief"—terminology stays locked in throughout. No confusion.

The Big One: Missing Template Reference Files

Your templates are listed but not lived in. You mention "Persona one-pager," "Discovery cheat sheet," and "Exec briefing note," but there are no actual reference files showing what these look like filled out. This kills your Progressive Disclosure Architecture score (23/30) because all the content is crammed into one file.

The fix: Create three new reference files:

• references/persona-one-pager-template.md — Show a completed CFO persona card with real pains, proof points, objections
• references/discovery-cheat-sheet.md — Multi-persona call example with how to thread between roles
• references/exec-briefing-example.md — Headline + outcome + ask format

This gets you +5 points and makes your skill way more actionable.

Other Things Worth Fixing

1. Add trigger phrases to your description. Right now it says "Use to summarize persona goals..." but doesn't include phrases like "run persona intel," "persona intel help," or "persona research." These matter for agent discoverability. +2 points

2. Fix the voice consistency. Your "When to Use" section mixes gerunds ("Preparing," "Equipping") with the imperative voice used elsewhere. Pick one and stick with it. "Prepare for discovery calls" reads better than "Preparing discovery calls." +1 point

3. Add a validation step. Your framework jumps straight to briefing without validating the persona card works. Add Step 6: Validation — "Review card with recent customer interactions; test questions in role-play; update with feedback from actual calls." +2 points

Quick Wins

• Add trigger phrases to description (+2)
• Create three reference template files (+5)
• Fix gerund/imperative voice consistency (+1)
• Add validation step to framework (+2)

These four moves get you from 79 to 89/100—solid B territory.

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.