vercel/vercel-plugin

is-agentic

Score how ready a website, domain, or public MCP endpoint is for AI agents using Is Agentic, and read or act on the resulting report.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/vercel/vercel-plugin --skill is-agentic

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Is Agentic

Is Agentic runs a technical audit of a public URL and publishes a 0 to 100 agent-readiness score with evidence-backed issues and recommended fixes. All interfaces below are public, read-only, and free; none needs an API key.

Get a score

Default: the official CLI. It returns a stored report immediately, or starts a scan and waits when none exists.

sh
npx is-agentic <domain> --json

Omit --json only when a human is reading the terminal output.

When you cannot run commands, use the read-only API instead. It never starts a scan; a 404 means no completed report exists yet.

GET https://is-agentic.com/api/v1/report?url=<url-encoded-target>

MCP hosts can connect to the Streamable HTTP endpoint https://is-agentic.com/mcp and call is_agentic_get_report, is_agentic_get_methodology, or is_agentic_get_developer_docs.

Read a report

The JSON response is a PublicScanReport:

  • score: 0 to 100, or null when the target could not be scored (for example an MCP server that requires authentication). score_label explains a null score.
  • score_breakdown.essential and .recommended: each has earned, available, passing, total. Essential checks are the ones that matter most; a site can look polished and still fail them.
  • score_breakdown.bonus: points and positive_signals. Bonus is additive and never required; do not treat missing bonus signals as defects.
  • issues[]: each has id, name, tier (essential | recommended | bonus), result (failed | partial), details (evidence from the scan), and recommendation (the fix).
  • report_url: the canonical human-readable report. Cite it when reporting a score to a person.
  • scanned_at: when the audit ran. Reports are immutable snapshots.

Improve a site's score

  1. Fetch the report for the exact target you are improving.
  2. Work through issues in this order: essential failures, essential partials, then recommended. Ignore bonus unless everything else passes.
  3. For each issue, details says what the scan observed and recommendation says what to change. Prefer the recommendation; it was written against the actual evidence.
  4. After deploying fixes, get a fresh score and compare scanned_at to confirm you are not reading the old snapshot (see gotchas).

Errors

Failures are RFC 9457 application/problem+json with a stable code and a resolution hint. Act on the code:

  • invalid_url (400): pass a public HTTP or HTTPS URL.
  • report_not_found (404): no completed report exists; create one with the CLI, or open https://is-agentic.com/scan/<target> to start a scan, then retry after it completes.
  • rate_limit_exceeded (429): honor Retry-After before retrying.
  • report_temporarily_unavailable (503): retry shortly; do not start a new scan.

Gotchas

  • Reports refresh only when a visit finds them older than 6 hours. Re-running the CLI right after deploying a fix returns the same stored snapshot; check scanned_at before drawing conclusions, and use the Rescan control on the report page when a human needs an immediate re-run.
  • The API and the CLI differ on missing reports: the API returns 404, the CLI starts a scan and waits. Pick accordingly.
  • Targets are exact: example.com/docs and example.com are separate reports, and a URL with a query string is its own report.
  • The rate limit is 120 requests per IP per 60 seconds.
  • For token-light reading, content pages and completed reports honor Accept: text/markdown.
같은 저장소의 Skills

더 많은 Skills

모든 Skills
vercel
공식

access-protected-vercel-deployment

Access and test Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection. Use when curl, agent-browser, Playwright, or another automated request reaches a Vercel login or protection page; when a protected preview or production URL returns 401 or 403; when TRUSTEDSOURCESENVIRONMENTMISMATCH appears; or when choosing between vercel curl and the x-vercel-trusted-oidc-idp-token header.

1시간 설치 수
1
GitHub Stars
341
업데이트
11월 20일
vercel
공식

client-side-security

Protect what runs in your users' browsers on Vercel with a Content-Security-Policy header and Page Integrity script monitoring. Use when adding or debugging a CSP, choosing where to set it (Next.js proxy.ts or next.config.js, vercel.json, Project Routes), allowing Vercel Toolbar under CSP, monitoring third-party scripts or tag managers, or meeting PCI DSS script requirements. For WAF rules and rate limits use vercel-firewall; for bots use botid.

1시간 설치 수
1
GitHub Stars
341
업데이트
11월 20일
vercel
공식

domains

Search, register, connect, transfer, and renew domain names on Vercel using the CLI or Domains Registrar API. Use for domain availability and pricing, custom domains, DNS records, nameservers, ownership verification, and domain orders.

1시간 설치 수
1
GitHub Stars
341
업데이트
11월 20일
vercel
공식

vercel-schedules

Vercel Schedules guidance — run a private function, route, or Vercel Queues topic on a cron cadence or once at a set time. Covers static schedules in vercel.json, dynamic per-user schedules with @vercel/schedules, handleSchedule, the vercel schedules CLI, environments, jitter, and migrating from Cron Jobs. Use when adding scheduled or recurring work, one-time reminders, or replacing crons.

1시간 설치 수
1
GitHub Stars
341
업데이트
11월 20일