Skip to content
Back to skills

Geo Transform

ASecurity

Use when proposing evidence-bounded readability and structure edits without inventing content, ranking claims, or structured data

  • 428 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 20, 2026
ai-agentsdocumentation

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 20, 2026

npx -y skills add aiskillstore/marketplace --skill geo-transform --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Geo Transform?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Geo Transform
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aiskillstore-geo-transform/badge)](https://www.skillsdirectory.com/skills/aiskillstore-geo-transform)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: geo-transform
description: Use when proposing evidence-bounded readability and structure edits without inventing content, ranking claims, or structured data
---

# GEO Transform — Evidence-Bounded Content Restructuring

Propose focused edits while preserving meaning, voice, provenance, and recoverability.

## Workflow

1. Read one authorized file and run the deterministic scan.
2. Classify each finding as an official requirement, deterministic check, heuristic, or experiment.
3. Show a focused diff before changing the file.
4. Change only what improves readability, factual provenance, or a documented technical requirement.
5. Rerun the same scan and report the reproducible output change separately from any external outcome.

## Allowed transformations

- Split a long paragraph where comprehension improves.
- Repair a genuinely confusing document outline; multiple H1 elements are not automatically wrong.
- Cite or remove unsupported quantitative claims.
- Reduce repetitive wording without changing meaning.
- Propose structured data only when it matches visible content and current documentation.
- Clarify genuine reader questions without auto-generating FAQ schema.

## Boundaries

- Never invent facts, statistics, sources, quotes, authors, dates, or benefits.
- Never describe a score increase as evidence of ranking, indexing, rich results, or citation.
- Never batch-transform files without explicit scope.
- Preserve a reviewable diff and the user's original voice.

Files in this skill

  • SKILL.md1.5 KB
  • skill-report.json8.3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…