diegosouzapw Kotler Macro-Environment Analyzer
Overview
This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/kotler-macro-analyzer from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
Kotler Macro-Environment Analyzer
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: How It Works, Limitations.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
- Use when conducting market entry research or a periodic strategic audit.
- Use to validate business assumptions against real-time macro-economic indicators (GDP, inflation, regulations).
- Use when preparing for high-level business planning sessions.
- Use when the request clearly matches the imported source intent: Professional PESTEL/SWOT analysis agent based on Kotler's methodology for strategic market audits.
- Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
- Use when provenance needs to stay visible in the answer, PR, or review packet.
Operating Table
| Situation | Start here | Why it matters |
|---|---|---|
| First-time use | metadata.json |
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow |
| Provenance review | ORIGIN.md |
Gives reviewers a plain-language audit trail for the imported source |
| Workflow execution | SKILL.md |
Starts with the smallest copied file that materially changes execution |
| Supporting context | SKILL.md |
Adds the next most relevant copied source file without loading the entire package |
| Handoff decision | ## Related Skills |
Helps the operator switch to a stronger native skill when the task drifts |
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
- Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
- Read the overview and provenance files before loading any copied upstream support files.
- Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
- Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
- Validate the result against the upstream expectations and the evidence you can point to in the copied files.
- Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
- Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.
Imported Workflow Notes
Imported: Overview
This skill transforms the agent into a senior strategic consultant specializing in Philip Kotler’s macro-marketing environment analysis. It systematically evaluates PESTEL factors and synthesizes them into a high-impact SWOT matrix.
Imported: How It Works
Step 1: Real-time Data Retrieval
The agent uses search tools to gather the latest economic, political, and legal data for the target region.
Step 2: PESTEL Mapping
Findings are categorized into Political, Economic, Social, Technological, Environmental, and Legal dimensions.
Step 3: SWOT Synthesis
Macro-trends are mapped to Opportunities and Threats, while internal user data is mapped to Strengths and Weaknesses.
Examples
Example 1: Ask for the upstream workflow directly
Use @kotler-macro-analyzer to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @kotler-macro-analyzer against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @kotler-macro-analyzer for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @kotler-macro-analyzer using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Imported Usage Notes
Imported: Examples
Example 1: Regional Market Entry
"Conduct a Kotler-style strategic audit for a renewable energy startup planning to enter the Eastern European market in 2026. Focus on regulatory shifts and green energy subsidies."
Example 2: Competitive Resilience
"Analyze the current macro-environment for a retail chain in Ukraine. Identify threats from inflation and opportunities from shifting consumer displacement trends."
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
- ✅ Always use search tools to verify specific economic indicators (e.g., current central bank rates).
- ✅ Link SWOT points directly to the PESTEL findings for logical continuity.
- ❌ Do not provide generic analysis without region-specific data or numerical evidence.
- Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
- Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
- Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
- Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
Imported Operating Notes
Imported: Best Practices
- ✅ Always use search tools to verify specific economic indicators (e.g., current central bank rates).
- ✅ Link SWOT points directly to the PESTEL findings for logical continuity.
- ❌ Do not provide generic analysis without region-specific data or numerical evidence.
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/kotler-macro-analyzer, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@00-andruia-consultant- Use when the work is better handled by that native specialization after this imported skill establishes context.@00-andruia-consultant-v2- Use when the work is better handled by that native specialization after this imported skill establishes context.@10-andruia-skill-smith- Use when the work is better handled by that native specialization after this imported skill establishes context.@10-andruia-skill-smith-v2- Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
| Resource family | What it gives the reviewer | Example path |
|---|---|---|
references |
copied reference notes, guides, or background material from upstream | references/n/a |
examples |
worked examples or reusable prompts copied from upstream | examples/n/a |
scripts |
upstream helper scripts that change execution or validation | scripts/n/a |
agents |
routing or delegation notes that are genuinely part of the imported package | agents/n/a |
assets |
supporting assets or schemas copied from the source package | assets/n/a |
Imported Reference Notes
Imported: Limitations
- Expert Review Required: This skill provides strategic frameworks but does not substitute for professional financial, legal, or management consulting.
- Data Freshness: The quality of the output depends on the real-time availability of data from search tools; results may vary in rapidly shifting economic environments.
- Scope: The analysis focuses on macro-level factors and does not include detailed internal operational auditing.