Hero construction
Skill obadadallo95/ai-native-portfolio-skills/skills/hero-construction
An opinionated skill system for AI-native builders who want portfolios with real identity, proof, taste, and AI discoverability.
npx -y skills add obadadallo95/ai-native-portfolio-skills --skill hero-constructionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Helps builders create a portfolio hero that establishes identity, authority, and relevance quickly without sounding generic, defensive, or over-explained.
SKILL.md
3.1 KB, 632 tokens by cl100k_base, as published. Nobody here has run it
Hero Construction
This skill exists because the hero is where a portfolio either earns attention or starts wasting it.
A strong hero should do three things quickly:
- tell me who this person is
- tell me why they matter
- tell me what kind of work or thinking I should expect
It should not behave like:
- a slogan wall
- a service-site intro block
- a defensive self-explanation
- a collection of clever labels with no center
Core Rule
A hero should establish authority before it expands context.
That means:
- strong primary statement first
- supporting proof second
- explanation only if needed
If the hero explains itself before it lands, it is weak.
What A Hero Must Usually Contain
A strong hero usually needs:
- a clear identity line
- a sharp headline
- one supporting layer of proof or framing
- one action path
Optional elements:
- portrait
- chips
- trust notes
- secondary CTA
Optional does not mean necessary.
What To Favor
- one sharp headline over multiple medium-strength ideas
- one supporting paragraph over stacked explanation layers
- one clear CTA over several equal-weight actions
- proof signals that reinforce the claim
- visual structure that gives the main line room to dominate
What To Avoid
- repeating the same idea in headline, subtitle, chips, and CTA note
- generic copy like "crafting digital experiences"
- too many technical labels before any real meaning lands
- hero sections that sound like a freelancer defending seriousness
- support copy that exists because the headline was not trusted enough
Hero Audit Questions
Before approving a hero, ask:
- Can I tell who this person is in one pass?
- Is the headline the strongest sentence on the screen?
- Is there too much explanation too early?
- If I remove one support layer, does the hero become cleaner?
- Does the CTA follow naturally from the positioning?
- Does the hero feel authored, or could it belong to anyone?
Common Failure Modes
Overloaded hero
Symptoms:
- too many proof strips
- too many micro-signals
- stacked copy layers
- too many decorative signals competing with the headline
Generic hero
Symptoms:
- broad service language
- startup-site cliches
- no real point of view
- clean layout with weak identity
Defensive hero
Symptoms:
- self-justification
- anxious explanation
- language trying to prove seriousness
- identity framed around anticipated criticism
Rewrite Method
When a hero feels weak:
- Find the one sentence that best expresses the builder's value.
- Promote it to the true headline.
- Remove one full support layer.
- Keep only the proof that sharpens the headline.
- Simplify the CTA so it matches the claim.
Success Condition
This skill succeeds when the hero feels like:
- an arrival point
- a clear authored presence
- a strong first judgment
Not:
- a decorated introduction
- a crowded confidence exercise