Competitive Cartographer
curiositech/some_claude_skills
Strategic analyst that maps competitive landscapes, identifies white space opportunities, and provides positioning recommendations.
This skill should be used when analyzing sector and industry performance charts to assess market positioning and rotation patterns.
$ npx skills add nicepkg/ai-workflow --skill sector-analyst -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nicepkg/ai-workflow sector-analyst --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/workflows/stock-trader-workflow/.claude/skills/sector-analyst .claude/skills/sector-analyst && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sector-analyst" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/stock-trader-workflow/.claude/skills/sector-analyst into .claude/skills/sector-analyst/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sector-analyst", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/nicepkg/ai-workflow/tree/main/workflows/stock-trader-workflow/.claude/skills/sector-analystType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add nicepkg/ai-workflow --skill sector-analyst -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nicepkg/ai-workflow sector-analyst --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/workflows/stock-trader-workflow/.claude/skills/sector-analyst .agents/skills/sector-analyst && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sector-analyst" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/stock-trader-workflow/.claude/skills/sector-analyst into .agents/skills/sector-analyst/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sector-analyst", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nicepkg/ai-workflow --skill sector-analyst -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nicepkg/ai-workflow sector-analyst --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/workflows/stock-trader-workflow/.claude/skills/sector-analyst .cursor/skills/sector-analyst && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sector-analyst" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/stock-trader-workflow/.claude/skills/sector-analyst into .cursor/skills/sector-analyst/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sector-analyst", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/nicepkg/ai-workflow.git --path workflows/stock-trader-workflow/.claude/skills/sector-analyst--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nicepkg/ai-workflow --skill sector-analyst -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nicepkg/ai-workflow sector-analyst --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/workflows/stock-trader-workflow/.claude/skills/sector-analyst .gemini/skills/sector-analyst && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sector-analyst" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/stock-trader-workflow/.claude/skills/sector-analyst into .gemini/skills/sector-analyst/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sector-analyst", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install nicepkg/ai-workflow sector-analystInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add nicepkg/ai-workflow --skill sector-analyst -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .github/skills && cp -r skills-src/workflows/stock-trader-workflow/.claude/skills/sector-analyst .github/skills/sector-analyst && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sector-analyst" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/stock-trader-workflow/.claude/skills/sector-analyst into .github/skills/sector-analyst/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sector-analyst", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nicepkg/ai-workflow --skill sector-analyst -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nicepkg/ai-workflow sector-analyst --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/workflows/stock-trader-workflow/.claude/skills/sector-analyst .opencode/skills/sector-analyst && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sector-analyst" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/stock-trader-workflow/.claude/skills/sector-analyst into .opencode/skills/sector-analyst/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sector-analyst", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
sector-analystThis skill should be used when analyzing sector and industry performance charts to assess market positioning and rotation patterns.
Sector Analyst is an agent skill from nicepkg/ai-workflow. This skill should be used when analyzing sector and industry performance charts to assess market positioning and rotation patterns. Use this skill when the user provides performance chart images (1-week or 1-month timeframes) for sectors or industries and requests market cycle assessment, sector rotation analysis, or strategic positioning recommendations based on performance data. All analysis and output are conducted in English.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files and assets (for example `references/sector_rotation.md`).
It sits in Marketing & SEO, covering Positioning and messaging. The repository describes itself as: 🚀 170+ pre-built skills for Claude Code, Cursor, Codex & 14+ AI tools. Stop re-teaching your AI the same things. One command → instant domain expertise. Marketing, SEO, Trading… The licence is MIT.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit d167b41. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Sector Analyst loads about 2.1k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 112 tokens; SKILL.md has 794 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from nicepkg/ai-workflow at commit d167b41, republished under its MIT licence (© nicepkg). 794 words, ~2,087 tokens.
.claude/skills/sector-analyst/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.This skill enables comprehensive analysis of sector and industry performance charts to identify market cycle positioning and predict likely rotation scenarios. The analysis combines observed performance data with established sector rotation principles to provide objective market assessment and probabilistic scenario forecasting.
Use this skill when:
Example user requests:
Follow this structured workflow when analyzing sector/industry performance charts:
First, carefully examine all provided chart images to extract:
Think in English while analyzing the charts. Document specific numerical performance figures for key sectors and industries.
Load the sector rotation knowledge base to inform analysis:
references/sector_rotation.md to access market cycle and sector rotation frameworksIdentify which cycle phase best matches current observations by:
Synthesize observations into an objective assessment:
Use data-driven language and specific references to performance figures.
Based on sector rotation principles and current positioning, develop 2-4 potential scenarios for the next phase:
For each scenario:
Scenarios should range from most likely (highest probability) to alternative/contrarian scenarios.
Create a structured Markdown document with the following sections:
Required Sections:
Save analysis results as a Markdown file with naming convention: sector_analysis_YYYY-MM-DD.md
Use this structure:
# Sector Performance Analysis - [Date]
## Executive Summary
[2-3 sentences summarizing key findings]
## Current Situation
### Market Cycle Assessment
[Which cycle phase and why]
### Performance Patterns Observed
#### 1-Week Performance
[Analysis of recent performance]
#### 1-Month Performance
[Analysis of medium-term trends]
#### Sector-Level Analysis
[Detailed breakdown by sector]
#### Industry-Level Analysis
[Notable industry-specific observations]
## Supporting Evidence
### Confirming Signals
- [List data points supporting cycle assessment]
### Contradictory Signals
- [List any conflicting indicators]
## Scenario Analysis
### Scenario 1: [Name] (Probability: XX%)
**Description**: [What happens]
**Outperformers**: [Sectors/industries]
**Underperformers**: [Sectors/industries]
**Catalysts**: [What would confirm this scenario]
### Scenario 2: [Name] (Probability: XX%)
[Repeat structure]
[Additional scenarios as appropriate]
## Recommended Positioning
### Strategic Positioning (Medium-term)
[Sector allocation recommendations]
### Tactical Positioning (Short-term)
[Specific adjustments or opportunities]
## Key Risks and Monitoring Points
[What to watch that could invalidate the analysis]
---
*Analysis Date: [Date]*
*Data Period: [Timeframe of charts analyzed]*When conducting analysis:
Apply these probability ranges based on evidence strength:
Total probabilities across all scenarios should sum to approximately 100%.
sector_rotation.md - Comprehensive knowledge base covering market cycle phases, typical sector performance patterns, and probability assessment frameworksSample charts demonstrating the expected input format:
sector_performance.jpeg - Example sector-level performance chart (1-week and 1-month)industory_performance_1.jpeg - Example industry performance chart (outperformers)industory_performance_2.jpeg - Example industry performance chart (underperformers)These samples illustrate the type of visual data this skill analyzes. User-provided charts may vary in format but should contain similar relative performance information.
© nicepkg, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files (references, assets) in workflows/stock-trader-workflow/.claude/skills/sector-analyst of nicepkg/ai-workflow.
Open the folder on GitHubat commit d167b41
Sector Analyst next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sector Analyst this skillnicepkg/ai-workflow | 285 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Competitive Cartographercuriositech/some_claude_skills | 244 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Competitor Intelgooseworks-ai/goose-skills | 1.2k | 1 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Smr Literature Positioningbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| List Architectswan-gtm/gtm-skills | 172 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Marketing OsYuzzyuk/marketing-os | 540 | — | ~2.5k | Automated safety check: Pass | MIT |
curiositech/some_claude_skills
Strategic analyst that maps competitive landscapes, identifies white space opportunities, and provides positioning recommendations.
gooseworks-ai/goose-skills
Competitor intelligence system. An agent skill from gooseworks-ai/goose-skills.
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning a Sociological Methods & Research (SMR) manuscript against the methods literature across sociology, statistics, econometrics, psychometrics, and…
swan-gtm/gtm-skills
A skill your agent uses when building B2B lead lists — ICP definition and scoring, sourcing companies, qualifying accounts, finding contacts, persona mapping, deduplication, and data validation.
Yuzzyuk/marketing-os
A complete marketing department in one skill. An agent skill from Yuzzyuk/marketing-os.
heliocosta-dev/revenue-centric-design
Playbook for designing SaaS and startup products that convert, retain, and monetize — landing pages & CRO, checkout & forms, onboarding/activation, churn reduction, pricing psychology, dashboards…
nicepkg/ai-workflow
Processes Drafts Pro captures from the Inbox folder. An agent skill from nicepkg/ai-workflow.
nicepkg/ai-workflow
Transform legacy codebases into AI-ready projects with Claude Code configurations.
nicepkg/ai-workflow
Writing coach that extracts educational content from your daily experiences and turns it into publish-ready newsletter drafts.
nicepkg/ai-workflow
Content web architecture framework. An agent skill from nicepkg/ai-workflow.
nicepkg/ai-workflow
Create complete Claude Code workflow directories with curated skills.
nicepkg/ai-workflow
Video/audio/image processing with FFmpeg and ImageMagick. An agent skill from nicepkg/ai-workflow.
Categories
This skill should be used when analyzing sector and industry performance charts to assess market positioning and rotation patterns. Sector Analyst is an agent skill from nicepkg/ai-workflow. This skill should be used when analyzing sector and industry performance charts to assess market positioning and rotation patterns.
Sector Analyst fits situations like: the user provides performance chart images (1-week; 1-month timeframes) for sectors; industries and requests market cycle assessment; sector rotation analysis.
Run `npx skills add nicepkg/ai-workflow --skill sector-analyst -a claude-code`. Or copy the skill folder (workflows/stock-trader-workflow/.claude/skills/sector-analyst in nicepkg/ai-workflow) into .claude/skills/sector-analyst in your project. Claude Code loads it when a task matches its description.
Run `npx skills add nicepkg/ai-workflow --skill sector-analyst -a codex`. Or copy the skill folder (workflows/stock-trader-workflow/.claude/skills/sector-analyst in nicepkg/ai-workflow) into .agents/skills/sector-analyst in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nicepkg/ai-workflow --skill sector-analyst -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sector-analyst, .gemini/skills/sector-analyst, .github/skills/sector-analyst and .opencode/skills/sector-analyst in your project.
SKILL.md names no scripts, command-line tools or credentials: Sector Analyst is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Sector Analyst is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.1k tokens (SKILL.md is roughly 8.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.6k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Sector Analyst: Competitive Cartographer (curiositech/some_claude_skills, 244 stars), Competitor Intel (gooseworks-ai/goose-skills, 1.2k stars), Smr Literature Positioning (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars) and List Architect (swan-gtm/gtm-skills, 172 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
nicepkg (a GitHub organization) maintains it in nicepkg/ai-workflow, which has 285 GitHub stars. The repository holds 75 skills in this directory. The repository was last updated on January 20, 2026.
Source: nicepkg/ai-workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.