用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/Varnan-Tech/opendirectory --skill geo-gap-fixer命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | geo-gap-fixer |
| description | Audit how often LLMs recommend your brand vs competitors and generate a GEO action plan. |
| category | GTM Intelligence |
| version | 1.0.0 |
Agent skill that audits LLM brand visibility and converts gaps into a concrete GEO content action plan.
Use this skill when a user wants to audit their Generative Engine Optimization (GEO) share-of-voice to know which LLM prompts their brand is losing, understand why competitors are recommended instead, and get a specific content fix plan.
Do NOT use this skill for: general SEO audits, paid ad optimization, or continuous social media monitoring. This is a point-in-time LLM visibility audit.
To run the audit, the user must provide API keys and a configuration file. Ensure the following are set up:
.env file (OPENAI_API_KEY, ANTHROPIC_API_KEY, GOOGLE_API_KEY, PERPLEXITY_API_KEY).pip install openai anthropic google-genaiconfig.json (copied from config.example.json) must contain:
brand_name (string, required)competitors (list of strings, required, 1-10 entries)category (string, required)buyer_intent_prompts (list of strings, optional. If empty, 20 prompts are auto-generated)target_llms (list of strings, optional)website_url (string, optional)Run the following scripts in order. Stop and ask for clarification if any script fails.
python scripts/probe_llms.py (Optional: append --dry-run to test config without API calls)
data/raw_responses.json.python scripts/analyze_results.py
data/analysis.json.python scripts/build_report.py
report/geo_audit_report.md and report/geo_audit_report.json.The primary output is report/geo_audit_report.md. Present its findings to the user.
Key Sections to Interpret:
Direct the user to the GEO Action Plan first, as it contains the concrete steps to fix the gaps identified in the audit.
If you encounter issues while executing the pipeline, follow these rules:
| Condition | Agent Action |
|---|---|
Missing config.json | Tell the user to copy config.example.json and fill it out. |
| Invalid JSON in config | Notify the user of the parse error location and ask them to fix it. |
| Missing required fields | List the exact missing fields (brand_name, competitors, category). |
| No API keys set | Ask the user to export at least 2 of the 4 supported API keys. |
| 1 API key only | Warn the user that results are less reliable, but proceed with the run. |
| Transient API failure | The script auto-retries. If it fails completely, it skips the provider. |
| Persistent API failure | The script skips the provider gracefully. Continue the pipeline. |
| Zero responses | The script exits non-zero. Notify the user to check API keys or config. |
| Missing upstream data file | Re-run the preceding script in the pipeline (e.g., probe before analyze). |
Limitations to keep in mind: