- Home
- Skills
- Marketing & SEO
- GEO Content Planner: Questions and Product Facts
GEO Content Planner: Questions and Product Facts
Turn supplied audience questions and product fact IDs into traceable opportunities and research gaps.
Free
Works with the AI Agents you already use
GEO Content Planner: Questions and Product Facts
Example session with this skill installed
Using geo-content-engine and the separately installed pinned CLI, run the plan example workflow from the bundled references/setup.md. Use only the bundled fictional examples, retain unknowns, and return the complete report. Do not infer live indexing or growth.
- Read your context and instructions
- Compiled the geo content planner
Verified local example
This is the complete report from the retained local CLI run on 2026-10-17 using the bundled fictional fixtures. It is not real product performance or an Agensi execution. Local absolute paths are displayed as [skill-directory]; report findings are unchanged.
plan report
FICTIONAL EXAMPLE — not a product measurement.
Generated: 2026-10-17T15:10:06.255Z
Supplied questions and fact references only; no traffic estimates or automatic publication.
Pass: 1; fail: 0; unknown: 0.
| Check | Status | Evidence | Next action |
|---|---|---|---|
| daily-journal | pass | [skill-directory]/examples/queries.yaml: How can I keep daily journal entries?; priority 1; daily-notes: https://example.com/features/daily-notes; sources not independently verified | Inspect sources and create distinct, useful content only when authorized. |
Details
{
"opportunities": [
{
"queryId": "daily-journal",
"query": "How can I keep daily journal entries?",
"intent": "use-case",
"priority": 1,
"facts": [
{
"id": "daily-notes",
"claim": "Save daily journal entries.",
"source": "https://example.com/features/daily-notes"
}
]
}
],
"researchGaps": []
}
Connects securely to your tools. The creator never sees your data.
About this skill
Turn supplied audience questions and product fact IDs into traceable opportunities and research gaps.
What you get
A free, MIT-licensed SKILL.md workflow from GEO Growth Engine, with setup references, limitations and fictional input examples. The ZIP contains instructions and supporting text; the executable CLI is installed separately.
Use cases
- Prioritize a supplied question list using product-fact IDs.
- Keep unsupported topics in a research-gap list.
Before you start
Node 24+, local shell/filesystem, separately installed pinned CLI; no sibling skill. Read the bundled references/setup.md before running the example. The required CLI is a pinned source-build candidate, not a published npm package.
Scope and limits
Source URLs are traceability pointers, not fetched verification; no demand, traffic or publishable-page promise. No paid provider API or connected store account is required.
Source and support
Pinned CLI source · Support and issues. Original source and MIT license remain publicly available on GitHub.
Source URLs are traceability pointers, not fetched verification; no demand, traffic or publishable-page promise. Node 24+, local shell/filesystem, separately installed pinned CLI; no sibling skill. Bundled data and the demo are fictional fixtures, not measured customer outcomes.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
1 use
Times used to date
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 1 month ago
- Free with an Agensi account
Requires
Permissions
Read only user-supplied configuration and relevant input files. Write reports and any copied evidence to the user-selected output directory. CLI workflows run locally without network collection. Initial source/dependency installation needs network access; no account credentials or paid API keys are required.