Resource submission: dnacore-check — CLI AI-readiness validator (npx, MIT)

## Tool Submission

**Name:** dnacore-check
**npm:** https://www.npmjs.com/package/dnacore-check
**Source:** https://github.com/dnacore-ai/dnacore-check
**Usage:** `npx dnacore-check https://yoursite.com`

## What it does

A zero-install CLI that checks three signals:

- `llms.txt` — validates presence and basic structure, scores up to 40pts
- `agents.json` — validates `/.well-known/agents.json` completeness, scores up to 25pts
- `robots.txt` — checks whether 11 major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.) are allowed, scores up to 20pts

Outputs an AI-Readiness Score (0–100) with grade (A+/A/B+/B/C/D) and actionable suggestions.

Optionally submits the site to the [DNACORE open protocol directory](https://dnacore.ai) — a verified registry of AI-native websites.

## Why CLI matters

Existing tools in this space (Citability, BridgeToAgent) are web scanners. A CLI/npx tool fits directly into developer workflows — CI pipelines, pre-deploy checks, local dev. No browser, no signup, no account.

MIT-licensed. No telemetry. Submission to DNACORE is opt-in (user types `y`).

Happy to adjust the implementation if anything looks off-spec.

Find the repository's existing resource-submission or directory-entry format, then compare dnacore-check's npm and source links with those conventions. Done means the submission is represented in the expected location with its name, usage, license, and description, or any missing acceptance requirements are identified.

Written by the indexing model from the issue text.