eeat-signals▌
kostja94/marketing-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Guides E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) implementation for SEO. E-E-A-T helps search engines and users assess content quality; YMYL topics (health, finance, legal) require higher E-E-A-T.
SEO Content: E-E-A-T Signals
Guides E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) implementation for SEO. E-E-A-T helps search engines and users assess content quality; YMYL topics (health, finance, legal) require higher E-E-A-T.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
What Is E-E-A-T
| Element | Meaning | Implementation |
|---|---|---|
| Experience | First-hand, real-world experience | Case studies, original research, user testimonials, "we tested" |
| Expertise | Subject-matter knowledge | Author credentials, expert quotes, technical depth |
| Authoritativeness | Recognition as a source | Backlinks, citations, author page, publisher reputation |
| Trustworthiness | Accuracy, transparency | Citations, About page, contact, HTTPS, no misleading content |
E-A-T (without Experience) is used in Featured Snippet context—Bing/Google emphasize correctness, document quality, then authority and trust. See featured-snippet.
Author Bio
| Element | Guideline |
|---|---|
| Placement | End of article or sidebar; link to author page |
| Content | Name, credentials, photo, brief expertise, link to author page |
| Author page | Dedicated page per author; bio, other articles, social |
| Schema | Person schema; link author to Article schema; see entity-seo |
Citations & References
| Scenario | Practice |
|---|---|
| Data or statistics | Cite source inline or in References section |
| Expert quotes | Attribute; link to source or profile |
| Reference section | For 5+ citations; list at end before Related posts |
| Format | Inline links preferred; numbered refs for academic-style |
| When to include | Any claim benefiting from authority (stats, studies, definitions) |
| External links | Link to reputable sources; avoid low-quality sites |
Experience Signals
| Signal | Use |
|---|---|
| Case studies | Real customer outcomes; Challenge→Solution→Results |
| Original research | First-party data, surveys, tests |
| First-hand testing | "We tested X"; product reviews with real use |
| User testimonials | Authentic quotes; link to full case study when available |
YMYL (Your Money Your Life)
Topics that can significantly impact health, financial stability, or safety require higher E-E-A-T:
- Health: Medical, mental health, nutrition advice
- Finance: Investment, tax, insurance, loans
- Legal: Legal advice, regulations
- Safety: Product safety, emergency procedures
Guidelines: Author credentials, citations to authoritative sources, clear sourcing, regular updates, avoid speculation.
AI-Assisted Content
When content is AI-assisted: human review before publish; verify facts and add citations; original insights or data; avoid generic phrasing. Transparency and human refinement support E-E-A-T.
Output Format
- E-E-A-T assessment (gaps, strengths)
- Author bio recommendation
- Citation plan (where to add, what to cite)
- Experience signals (case studies, original data)
- YMYL considerations (if applicable)
Related Skills
- article-page-generator: Article page structure; author bio placement
- article-content: Article body creation; citations, references format
- content-optimization: Original images, content quality; E-E-A-T complements
- link-building: Digital PR, E-E-A-T; backlinks signal authority
- featured-snippet: E-A-T in snippet algorithm; correctness, authority
- backlink-analysis: Authority assessment; E-E-A-T context
- customer-stories-page-generator: Case studies as experience signal
- testimonials-generator: User quotes as trust signal
- entity-seo: Entity signals; Organization, Person schema; Knowledge Panel; E-E-A-T alignment
How to use eeat-signals on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add eeat-signals
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches eeat-signals from GitHub repository kostja94/marketing-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate eeat-signals. Access the skill through slash commands (e.g., /eeat-signals) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★64 reviews- ★★★★★Isabella White· Dec 24, 2024
Registry listing for eeat-signals matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Nia Thompson· Dec 24, 2024
eeat-signals has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Kofi Wang· Dec 16, 2024
eeat-signals reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Kofi Yang· Dec 4, 2024
Useful defaults in eeat-signals — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Aisha Menon· Nov 15, 2024
Keeps context tight: eeat-signals is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Layla Tandon· Nov 15, 2024
eeat-signals fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Kofi Chen· Nov 11, 2024
I recommend eeat-signals for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Nikhil Gupta· Nov 7, 2024
eeat-signals is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Nia Desai· Oct 26, 2024
Keeps context tight: eeat-signals is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Isabella Farah· Oct 6, 2024
eeat-signals is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 64