사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/agricidaniel/codex-seo --skill seo-visual시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Visual Specialist
Use this for the visual sub-track in full audits.
Shared Data Cache
Step 0 -- Check shared data cache:
Before gathering, check .seo-cache/ for cached data from other skills. Reference: ../seo/references/shared-data-cache.md for schemas and dependency map.
This specialist does not require upstream cache inputs before running fresh visual checks.
- If found: no prerequisite cache is needed; continue with current visual capture workflow
- If missing: proceed normally and gather fresh visual data
- If JSON is corrupt or unreadable: treat it as missing and continue normally
- If the user says "refresh" or "re-run": ignore cache entirely
Inputs
- URL
- Timeout
- Visual mode (
on|off|auto)
Outputs
VISUAL-AUDIT-REPORT.mdSUMMARY.jsonscreenshots/(if Playwright available)
Checks
- H1 and CTA visibility above the fold
- Mobile viewport + horizontal scroll
- Touch target sizing and minimum font size
- Multi-viewport screenshots
Write to shared data cache
After completing all work, write results to .seo-cache/.
mkdir -p .seo-cache/pages/{url-slug}Write .seo-cache/pages/{url-slug}/visual.json using the schema in ../seo/references/shared-data-cache.md. Preserve the documented top-level keys: cache_type, analyzed_at, url, url_slug, score, layout_summary, and issues. Add extra visual detail only as supplemental fields, such as above_fold, mobile, screenshots, or notes.
Add .seo-cache/ to .gitignore if not already present:
grep -qxF '.seo-cache/' .gitignore 2>/dev/null || echo '.seo-cache/' >> .gitignorePremium Deliverable
If the user requests a 'client report' or 'premium deliverable', automatically read ../seo-audit/assets/report-template.html and ../seo/references/premium-report-standard.md. Use that report standard as the default brief. Generate the HTML as an internal intermediate artifact, then produce the PDF as the public deliverable. Mention only the PDF in your final response unless the user explicitly asks for the HTML file.
