Skills geo-fundamentals

📦

geo-fundamentals

Name: geo-fundamentals
Author: sickn33

Content revision r2 Safe ⚙️ External commands

Improve Content for AI Search Citations

Web content often lacks the structure and attribution that AI search engines use when selecting citations. This skill explains GEO practices and audits public web pages for citation readiness.

Supports: Claude Codex Code(CC)

📊 75 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "geo-fundamentals" from https://skillstore.io/skills/sickn33-geo-fundamentals.md and its manifest at https://skillstore.io/api/skills/sickn33-geo-fundamentals/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-geo-fundamentals.md Signed manifest GET /api/skills/sickn33-geo-fundamentals/manifest Signed lockfile GET /api/skills/sickn33-geo-fundamentals/lockfile

Test it

Using "geo-fundamentals". Explain why my article has weak GEO readiness.

Expected outcome:

The page lacks author attribution and publication dates.
No JSON-LD identifies the article or its publisher.
Add direct definitions, sourced statistics, and an FAQ section.

Using "geo-fundamentals". Prioritize fixes for a page with no H1, no structured data, and one H2.

Expected outcome:

Add one descriptive H1 that states the page topic.
Add relevant JSON-LD with accurate article, author, and date fields.
Create additional H2 sections around distinct user questions.

Using "geo-fundamentals". Create a GEO checklist for a product comparison article.

Expected outcome:

State the comparison criteria and define important terms.
Use a readable table with current, sourced data.
Name the author, show update dates, and answer common questions.

Security Audit

Safe

v5 • 7/23/2026 Open versioned report

The only static finding is a false positive: SKILL.md line 157 contains a Markdown-formatted usage command, not Ruby or shell execution. No prompt injection, data exfiltration intent, or other semantic security issue was found in the reviewed files.

Files scanned

456

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (1)

SKILL.md:157

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/sickn33-geo-fundamentals/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-geo-fundamentals/security.svg)](https://skillstore.io/skills/sickn33-geo-fundamentals?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-geo-fundamentals?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-geo-fundamentals/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-geo-fundamentals.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). geo-fundamentals security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-geo-fundamentals/audits/5

BibTeX citation

@techreport{sickn33-sickn33-geo-fundamentals-2026,
  author = {sickn33},
  title = {geo-fundamentals security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/sickn33-geo-fundamentals/audits/5},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "geo-fundamentals security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
  - name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-geo-fundamentals/audits/5"
identifiers:
  - type: other
    value: "skillstore:sickn33-geo-fundamentals:audit:5"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Plan Citable Articles

Build article briefs with clear definitions, sourced data, expert attribution, FAQs, and structured sections.

Audit Web Components

Review HTML, JSX, and TSX pages for structural signals that support AI retrieval and citation.

Prioritize GEO Improvements

Compare page scores and reported issues to focus optimization work across a website.

Try These Prompts

Learn GEO Basics

Explain GEO for a beginner. Compare it with SEO and list five content elements that improve AI citation readiness.

Review a Page Plan

Review this page outline for GEO readiness: [outline]. Identify missing definitions, sources, author details, dates, FAQs, lists, and structured data.

Interpret an Audit

Interpret this GEO checker output: [results]. Prioritize the three most important improvements and explain how each addresses a reported issue.

Design a Sitewide GEO Program

Create a sitewide GEO improvement plan for [site]. Use [audit results], audience needs, content ownership, implementation effort, and measurable citation-readiness indicators.

Best Practices

Validate automated findings against rendered pages because dynamic content may not appear in source scans.
Support claims with named, current sources and keep author and date information accurate.
Use the score to prioritize review, then measure real citations and AI-referred traffic separately.

Avoid

Do not present unsourced statistics or invented expert quotes to improve apparent authority.
Do not treat a high checker score as proof that an AI engine will cite a page.
Do not add irrelevant schema, repetitive FAQs, or excessive headings only to satisfy checks.

Frequently Asked Questions

What is Generative Engine Optimization?

GEO improves content clarity, structure, attribution, and machine-readable context for retrieval and citation by AI-powered search systems.

Which files does the checker inspect?

It inspects likely public pages in HTML, HTM, JSX, and TSX files, while skipping common build, test, documentation, and dependency directories.

Does the checker access the internet?

No. The included script reads local project files and prints audit results to the console.

Does a high score guarantee AI citations?

No. The score measures detected page elements, not authority, retrieval performance, ranking, or actual citation outcomes.

Can it audit a deployed website directly?

No. Provide a local project path containing the website source files.

How should teams use the reported issues?

Review each issue against the rendered page, prioritize meaningful content gaps, implement accurate changes, and track real citation results separately.