Back to skills
SkillHub ClubResearch & OpsFull Stack
dellight-intelligence-ops
Imported from https://github.com/openclaw/skills.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Stars
3,111
Hot score
99
Updated
March 20, 2026
Overall rating
C0.0
Composite score
0.0
Best-practice grade
F32.4
Install command
npx @skill-hub/cli install openclaw-skills-dellight-intelligence-ops
Repository
openclaw/skills
Skill path: skills/arthurelgindell/dellight-intelligence-ops
Imported from https://github.com/openclaw/skills.
Open repositoryBest for
Primary workflow: Research & Ops.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: openclaw.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install dellight-intelligence-ops into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/openclaw/skills before adding dellight-intelligence-ops to shared team environments
- Use dellight-intelligence-ops for development workflows
Works across
Claude CodeCodex CLIGemini CLIOpenCode
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
---
name: cio-intelligence
description: Chief Intelligence Officer operations for AI startups. Use for market intelligence gathering, competitive analysis, technology trend monitoring, signal detection, opportunity assessment, threat identification, and strategic intelligence briefings.
# CIO Intelligence Operations
## Role Definition
The CIO gathers, analyzes, and delivers actionable intelligence to inform revenue decisions and strategic positioning. Reports to CEO with dotted line to CRO.
## Intelligence Priorities
### Tier 1: Immediate Revenue Impact
- Competitor pricing and positioning changes
- New market entrants in your product categories
- Customer signals (RFPs, job postings indicating need)
- Platform changes (App Store policies, algorithm shifts)
### Tier 2: Strategic Positioning
- Frontier model releases that enable or threaten your products
- Regulatory developments (AI regulation, data privacy)
- Partnership opportunities (agencies, platforms, enterprises)
- Market sizing updates for your product categories
### Tier 3: Horizon Scanning
- Emerging AI capabilities that could become products
- Adjacent market opportunities
- Technology convergence trends
- Talent market signals
## Intelligence Collection Framework
### Daily Scan
Collect signals from configured intelligence sources:
- Technology trending topics
- Competitive landscape changes
- Market sentiment shifts
### Sources
Configure these source types for your domain:
| Source | Signal Type | Frequency |
|--------|-----------|-----------|
| GitHub Trending | Competitor/tech signals | Daily |
| HackerNews | Industry sentiment | Daily |
| LinkedIn | Competitor activity | Daily |
| AI newsletters | Landscape changes | Daily |
| ArXiv | Research breakthroughs | Weekly |
| App stores | Competitor apps | Weekly |
| Crunchbase | Funding signals | Weekly |
### Competitive Intelligence Matrix
For each competitor, track: [references/competitive-framework.md](references/competitive-framework.md)
### Signal Classification
| Signal | Action | Urgency |
|--------|--------|---------|
| Direct competitor launch | Immediate CRO briefing | Hours |
| Frontier model release | Assess product impact | 24 hours |
| Market trend shift | Weekly intelligence brief | Weekly |
| Horizon opportunity | Monthly strategic review | Monthly |
## Intelligence Products
### Daily Brief
- 3-5 bullet points of overnight signals
- One actionable recommendation
- Risk/opportunity flag if applicable
### Weekly Intelligence Report
- Competitive landscape changes
- Technology shifts affecting products
- Market opportunity assessment
- Recommended strategic actions
### Ad-Hoc Alerts
- Triggered by high-urgency signals
- Direct notification to CEO + CRO
- Include: what happened, impact assessment, recommended action
## Decision Support
When asked to evaluate a technology or market decision:
1. **Gather**: Collect data from all available sources
2. **Analyze**: Cross-reference signals, identify patterns
3. **Assess**: Rate impact (1-5) and confidence (1-5)
4. **Recommend**: Provide clear recommendation with reasoning
5. **Monitor**: Set up ongoing tracking for the decision area
Reference: [references/decision-framework.md](references/decision-framework.md)
---
## Referenced Files
> The following files are referenced in this skill and included for context.
### references/competitive-framework.md
```markdown
# Competitive Intelligence Framework
## Competitor Tracking Template
For each competitor, maintain:
- Name: Company/product name
- Category: Which of our products it competes with
- Funding: Total raised, last round, investors
- Pricing: Published pricing tiers
- Positioning: How they describe themselves
- Differentiation: What they claim is unique
- Weaknesses: Known limitations, customer complaints
- Threat Level: High / 🟡 Medium / 🟢 Low
- Last Updated: Date of last assessment
## Known Competitive Landscape
### Media Production Engine Competitors
- **Synthesia**: AI video with avatars. Enterprise focus. $67M Series C. Expensive.
- **HeyGen**: AI avatar videos. Simpler, lower price point. Consumer/SMB.
- **Runway**: Creative AI tools. Strong brand. Developer-focused.
- **Pika**: AI video generation. Consumer-focused. Limited enterprise features.
- **Descript**: Video editing with AI. Established player. Not full production.
**Our differentiation**: Full production pipeline (script→voice→visual→edit), not just one capability. Enterprise-grade. Local/sovereign deployment option.
### Superhuman X Competitors
- **Otter.ai**: Meeting transcription, conversation intelligence
- **Fireflies.ai**: Similar space
- **Android native**: Google's built-in AI features expanding
### GAZE Competitors
- **Character.AI**: Digital companions. Large user base but different positioning.
- **Replika**: Companion chatbot. Consumer.
## Disruption Watch
### Frontier Model Threats
- Every major model release can obsolete a product feature
- **Mitigation**: Build on WORKFLOW, not on MODEL CAPABILITY
- Products that orchestrate (like OpenClaw) survive; products that wrap (simple API frontends) die
### SaaS Displacement Pattern
1. New model launches with capability X
2. 100 startups build wrapper around capability X
3. Next model version makes capability X trivial/free
4. Wrapper startups die
5. **Survivors**: Those who built workflow, data moats, or distribution
**Our strategy**: Build products that leverage ANY model, not depend on ONE model.
```
### references/decision-framework.md
```markdown
# Technology & Market Decision Framework
## RAPID Decision Model (Adapted for AI Startup)
**R**ecommend, Person=CIO / CRO, Responsibility=Propose the decision with supporting data
**A**gree, Person=CRO (commercial) / CTO (technical), Responsibility=Must agree for decision to proceed
**P**erform, Person=Assigned team/agent, Responsibility=Execute the decision
**I**nput, Person=CMO, CFO, Responsibility=Provide data and perspective
**D**ecide, Person=CEO (Arthur), Responsibility=Final authority on strategic decisions
## Decision Evaluation Matrix
Score each option on:
Revenue impact (30 days), Weight=30%, Score (1-5)=
Revenue impact (90 days), Weight=20%, Score (1-5)=
Competitive advantage, Weight=15%, Score (1-5)=
Implementation effort, Weight=15%, Score (1-5)=
Risk of disruption, Weight=10%, Score (1-5)=
Strategic alignment, Weight=10%, Score (1-5)=
**Weighted Score = ÎŁ (Weight Ă— Score)**
## Speed of Decision
Tactical (tool choice, content topic), Max Time=Immediate, Who Decides=CRO/CMO
Operational (pricing change, campaign launch), Max Time=24 hours, Who Decides=CRO + CEO
Strategic (new product, pivot, partnership), Max Time=72 hours, Who Decides=CEO with CRO input
Existential (funding, company direction), Max Time=1 week, Who Decides=CEO
**Default**: If in doubt, decide faster. Reversible decisions should take minutes, not days.
```
---
## Skill Companion Files
> Additional files collected from the skill directory layout.
### _meta.json
```json
{
"owner": "arthurelgindell",
"slug": "dellight-intelligence-ops",
"displayName": "DELLIGHT Intelligence Operations",
"latest": {
"version": "1.0.0",
"publishedAt": 1771065228419,
"commit": "https://github.com/openclaw/skills/commit/46c14dfd72702fff0e23fa413299cfe851626148"
},
"history": []
}
```