| id | SKL-analyst-ANALYSTRELATIONS |
| name | Analyst Relations |
| description | Analyst Relations enables managing relationships with industry analysts, briefings, and research reports. This capability is essential for building market credibility, influencing analyst reports, sup |
| version | 1.0.0 |
| status | active |
| owner | @cerebra-team |
| last_updated | 2026-02-22 |
| category | Backend |
| tags | ["api","backend","server","database"] |
| stack | ["Python","Node.js","REST API","GraphQL"] |
| difficulty | Intermediate |
Analyst Relations
Skill Profile
(Select at least one profile to enable specific modules)
Overview
Analyst Relations enables managing relationships with industry analysts, briefings, and research reports. This capability is essential for building market credibility, influencing analyst reports, supporting sales cycles, and driving market awareness.
Why This Matters
Strategic Necessity:
- Market Credibility: Build credibility with analysts through consistent engagement
- Influence: Influence analyst reports and coverage to benefit your product
- Sales Support: Support sales with analyst interactions and insights
- Market Awareness: Increase market visibility through analyst relationships
- Competitive Intelligence: Gather competitive insights from analyst briefings
Core Concepts & Rules
1. Core Principles
- Follow established patterns and conventions
- Maintain consistency across codebase
- Document decisions and trade-offs
2. Implementation Guidelines
- Start with the simplest viable solution
- Iterate based on feedback and requirements
- Test thoroughly before deployment
Inputs / Outputs / Contracts
- Inputs:
- <e.g., env vars, request payload, file paths, schema>
- Entry Conditions:
- <Pre-requisites: e.g., Repo initialized, DB running, specific branch checked out>
- Outputs:
- <e.g., artifacts (PR diff, docs, tests, dashboard JSON)>
- Artifacts Required (Deliverables):
- <e.g., Code Diff, Unit Tests, Migration Script, API Docs>
- :
