Index of every page on this site: llms.txt
All skills
alptugharun avatar

/maps-opportunity-radar

@2b12408
Run it yourself

Researches Google Maps, Places, Business Profile, geospatial AI, MCP, ChatGPT, Claude and Agent Skill opportunities to identify under-served map workflows. Use when the user asks what Maps-related product, skill, automation or repository to build next.

  • 1 file
  • 3.9 KB
  • MIT
  • Updated 2 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/alptugharun/ai-social-media-toolkit/maps-opportunity-radar

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈69 tokens for metadata: the name and description. ≈909 when used: this file.

Description uses 3.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈277 characters, or 3.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Maps Opportunity Radar

Find evidence-backed Maps + AI opportunities without pretending novelty or virality can be guaranteed.

Required References

Read:

  • references/EVIDENCE-POLICY.md
  • references/GITHUB-GROWTH-PLAYBOOK.md
  • references/MAPS-AI-OPPORTUNITY-PLAYBOOK.md

Research Scope

Inspect fresh signals across:

  • Google Maps Platform
  • Places API
  • Places Aggregate API
  • Google Business Profile APIs
  • Google Maps Agent Skills
  • Google Maps MCP projects
  • ChatGPT + Maps
  • Claude + Maps
  • Codex + Maps
  • Gemini + Maps
  • local SEO
  • local-rank tracking
  • geospatial agents
  • creator-location tools
  • Timeline / Takeout tooling
  • MapLibre / open geospatial tooling

Core Questions

  1. What official capability already exists?
  2. What strong open-source project already solves the basic job?
  3. Which user still has an unsolved workflow?
  4. Can the result be measured or demonstrated?
  5. Can it be built without scraping or prohibited data storage?
  6. Is it useful to creators, agencies, local businesses or developers?
  7. Does it fit this repository, or should it be a separate product?

Novelty Rule

Never say:

Nobody has ever built this.

unless comprehensive evidence actually supports that statement.

Prefer:

Direct competition appears limited for this specific job based on the current search sample.

Viral / Revenue Rule

Never promise:

  • virality
  • one million users
  • sponsorship
  • revenue
  • GitHub Trending placement

Instead identify the mechanics that could improve distribution:

  • sharp problem
  • fast first result
  • shareable output
  • proof
  • portability
  • low setup friction
  • trust
  • timing

Competitor Teardown

For each strong competitor capture:

  • repository
  • stars
  • forks
  • update recency
  • one-line promise
  • install friction
  • tools / workflows
  • proof
  • licensing
  • missing workflow

Candidate Score

Use a transparent heuristic:

  • 25% demand evidence
  • 20% direct-supply gap
  • 20% strategic fit
  • 15% proof potential
  • 15% compliance feasibility
  • 5% distribution ease

Apply a strong penalty to a generic Google Maps MCP wrapper if an existing official or mature implementation already covers the same job.

Policy Gate

Before recommending a build, run the concept through maps-policy-guard.

Reject or redesign concepts that depend on:

  • consumer Maps UI scraping
  • prohibited bulk export / permanent storage
  • hidden Street View harvesting
  • auto-spam outreach
  • sensitive-trait inference
  • fabricated review activity

Output

Maps Opportunity Radar

Evidence Window

  • Date:
  • Sources:
  • Confidence:

Official Capability Baseline

Capability Official option Implication

Open-Source Competitor Snapshot

Repository Signal Strength Gap

Demand / Supply Proxies

Theme Demand signal Direct supply Interpretation

Opportunity Candidates

Candidate User Job Evidence Compliance Score

Best Prototype

  • Name:
  • User:
  • Problem:
  • Why now:
  • Input:
  • Output:
  • Proof contract:
  • Install / run path:
  • Policy status:

Separate-Product Candidates

List ideas that should not be forced into this repository.

Human Review Gate

  • Current official docs checked
  • Strong competitors checked
  • No fake novelty claim
  • No guaranteed virality claim
  • Policy architecture reviewed
  • Human approval required before publishing a new skill or product

Core Principle

Find the missing workflow above the map API, not another wrapper around the same endpoints.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 2b12408. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 days ago.

Activeupdated 2 months ago
metadata
{
  "version": "0.1.0",
  "author": "Alptuğ Harun"
}

README badge

README badge for alptugharun/ai-social-media-toolkit/maps-opportunity-radar