Use when previewing optional llms.txt proposal files, candidate JSON-LD, or crawler-control suggestions for a website build
Pro scans all 2 files and shows the line behind each finding
Scanned 9/20/2026
npx -y skills add aiskillstore/marketplace --skill geo-generate --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Geo Generate?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/aiskillstore-geo-generate)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: geo-generate
description: Use when previewing optional llms.txt proposal files, candidate JSON-LD, or crawler-control suggestions for a website build
---
# GEO Generate — Optional Discovery Artifacts
Generate reviewable candidate artifacts. These files do not guarantee crawling, indexing, search features, visibility, or citation.
## Workflow
1. Identify an authorized static build directory.
2. Preview without writing:
```bash
npx geoptimize generate <directory> --dry-run
```
3. Review every output:
- `llms.txt` and `llms-full.txt` are experiments based on a proposal.
- Candidate `Article` or `BreadcrumbList` JSON-LD must match visible content.
- Crawler rules have service-specific meanings; an allow rule is not an outcome guarantee.
4. Write only after the user approves the exact directory:
```bash
npx geoptimize generate <directory>
```
## Boundaries
- Never overwrite an existing artifact without confirmation and a recoverable copy.
- Never infer `FAQPage` from question headings.
- Never add `<link rel="llms-txt">` as if it were a standardized discovery mechanism.
- Never auto-apply `robots.txt` suggestions.
- Validate structured data against current primary documentation before deployment.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!