Skip to content

Backfill repo manifests on main (agent card + per-category READMEs)#313

Merged
fahadadeel merged 2 commits into
mainfrom
docs/backfill-manifests-20260624T150441
Jun 24, 2026
Merged

Backfill repo manifests on main (agent card + per-category READMEs)#313
fahadadeel merged 2 commits into
mainfrom
docs/backfill-manifests-20260624T150441

Conversation

@agent-aspose-pdf-examples

Copy link
Copy Markdown
Collaborator

Summary

Closes the HIGH-severity findings from a SEO/GEO Agent audit on this repo (Overall 45 / Poor, Discovery 0, SEO 38):

  • No /.well-known/agent.json — agent directories / LangChain hubs / Postman / n8n cannot auto-discover the repo
  • No llm.txt — AI crawlers (ChatGPT, Perplexity, Claude) miss the repo on standard manifest paths
  • 0/34 categories have dedicated pages — the audit checks for README.md per folder (what GitHub renders by default), not AGENTS.md

Changes

File Status Purpose
.well-known/agent.json new Agent card with capabilities, MCP endpoint, stats, manifests
llm.txt new AI-crawler-discoverable repo summary (existed in generator code but never shipped to main)
<category>/README.md × 34 new Human + SEO twin of the existing per-category AGENTS.md
index.json refreshed Root machine-readable manifest
AGENTS.md (root + several per-cat) refreshed Minor content drift since the previous regen

73 files changed, 3615 insertions, 214 deletions. No code, tests, or LICENSE.txt touched.

How generated

One-shot run of scripts/regen_main_docs.py from the aspose-pdf-api-v2 sibling repo, using the same generators as the production update_repo_docs path. The agent-card + per-category README generators are from gitlab MR !48 (pending merge); identical code, just executed standalone here so main doesn't wait for the 26.6.0 release cycle.

Test plan

  • Local diff inspected — no LICENSE.txt / unrelated churn
  • Agent card validates as JSON, schema_version present, MCP endpoint pass-through correct
  • Per-category READMEs link back to AGENTS.md + root
  • After merge: re-run the SEO/GEO audit — Discovery and SEO scores should move into the Good range
  • After merge: spot-check that GitHub renders the per-category README.md when navigating into a folder

AI-assisted development

SEO/GEO audit on aspose-pdf/agentic-net-examples scored Overall 45
(Poor) -- Discovery=0, SEO=38 -- with HIGH-severity findings dominated
by "no /.well-known/agent.json", "no AI manifest (llm.txt)", and
"0/34 categories have dedicated pages (README.md)."

This commit closes those gaps without waiting for the next release
cycle:

- /.well-known/agent.json -- agent card with capabilities, MCP endpoint,
  manifests, stats. Lets LangChain hubs / Postman / n8n / agent
  directories auto-discover the repo.
- 34 x <category>/README.md -- the human-facing twin of the existing
  AGENTS.md, what GitHub renders by default when navigating into the
  folder. Each carries a keyword-rich SEO lead, example list, and
  back-links to the category AGENTS.md + root.
- llm.txt -- the AI-crawler-discoverable repo summary. Existed in the
  generator code but never shipped to main.
- index.json + AGENTS.md refreshed against the current main snapshot
  (26.5.0, 2,648 examples, 34 categories).

Generated by scripts/regen_main_docs.py (one-shot) running the same
generators as the production update_repo_docs path. Re-running the
audit after this merges should lift Discovery and SEO into the
"Good" range.

AI-assisted development
Bugs in the initial agent.json on this branch:
- mcp_endpoint used https:// but production MCP serves only http:// on
  port 7002 -- consumers would 404 immediately
- Missing api_base_url, openapi_url, docs_url -- all available on the
  PDF MCP at /openapi.json and /docs (verified 200 publicly)
- Missing tools enumeration -- agent directories need this to route
- Categories were just names; per-category example counts let
  directory previews show coverage at a glance

New top-level shape: {name, version, url, api_base_url, mcp_endpoint,
openapi_url, docs_url, capabilities, tools, categories: [{name,
examples}], product, links}.

Surfaces the four PDF MCP endpoints (agent_generate, agent_run,
generate, retrieve) so consumers can pick the right entry point
without first crawling /openapi.json.

AI-assisted development
@agent-aspose-pdf-examples agent-aspose-pdf-examples force-pushed the docs/backfill-manifests-20260624T150441 branch from 8ff52dd to 34b8657 Compare June 24, 2026 10:17
@fahadadeel fahadadeel merged commit c7b67c2 into main Jun 24, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants