[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WVQ0ANQQSFB2TT097D24BN":3,"skill-same:01M6WVQ0ANQQSFB2TT097D24BN":172},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M6WVQ0ANQQSFB2TT097D24BN","hyper-seo",null,"[Hyper] Use this skill when the user asks for an SEO, AEO, GEO, or LLMO audit, an optimization report, a new-site launch setup plan, or a score-improvement loop for a named target. Covers on-page, technical, content, Core Web Vitals, answer-engine, generative-engine, AI search visibility, AI crawler policy, metadata, and citation readiness, saved under `.hyper\u002Fseo\u002F[slug]\u002F`. Do not use it for page or product design, release gating, pure performance work with no search context, or market research with no target site.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"hyper seo","seo","hyper","inspection","new","write","release","read","audit","product","plan","work","browser","when","access","gating","loop","design","local","search","performance","vitals","generative","2026-11-10 10:12:30",false,"---\nname: hyper-seo\ndescription: \"[Hyper] Use this skill when the user asks for an SEO, AEO, GEO, or LLMO audit, an optimization report, a new-site launch setup plan, or a score-improvement loop for a named target. Covers on-page, technical, content, Core Web Vitals, answer-engine, generative-engine, AI search visibility, AI crawler policy, metadata, and citation readiness, saved under `.hyper\u002Fseo\u002F[slug]\u002F`. Do not use it for page or product design, release gating, pure performance work with no search context, or market research with no target site.\"\ncompatibility: Works best with live web access, browser inspection, local source search, Lighthouse or Core Web Vitals data when available, and read\u002Fwrite access for report artifacts.\n---\n\n@rules\u002Fseo-workflow.md\n@rules\u002Fvalidation.md\n\n# Hyper SEO\n\n> Audit and improve a project's search visibility across traditional search engines and AI answer engines.\n\n\u003Cinstruction_contract>\n\n| Field | Contract |\n|---|---|\n| Intent | Produce an evidence-graded SEO\u002FAEO\u002FGEO\u002FLLMO audit and a prioritized, actionable optimization report for a named target, produce a phased setup plan when a site or homepage is being planned or launched, and drive a bounded score-improvement loop when the user asks for the best achievable score. |\n| Scope | Owns target classification, measurement-method selection, on-page\u002Ftechnical\u002Fcontent\u002FCore Web Vitals\u002FAEO\u002FGEO\u002FLLMO assessment, new-site setup planning, scoring, findings, recommendations, and the report workspace. Does not own implementation outside the audited target, release gating, page or product design, account actions that need the owner's credentials unless permitted, or broad market research that has no target site or content set. |\n| Authority | System\u002Fharness and user instructions > the audited target's own files and live observations > official platform documentation > this skill > heuristic preference. A tool, lab, synthetic, or heuristic observation is never promoted to an official requirement. |\n| Evidence | Read the target's own files, rendered pages, and live responses before scoring, and cite the command, URL, file path, or probe result behind every critical and warning finding. Record unavailable checks as `unknown` and irrelevant checks as `not-applicable`; never invent a score, a ranking, an inclusion, or a citation. |\n| Tools | Use available read\u002Fsearch\u002Fbrowser tools, and render the dashboard with `bash scripts\u002Frender-dashboard.sh \u003Cartifact-dir>`. Web search, browser inspection, field Core Web Vitals, Search Console, or an AI citation probe are used only when actually available; when one is missing, state the capability limit and fall back to the strongest lower-grade method. |\n| Loop | Optimize mode only: a bounded `audit -> fix or recommendation -> re-audit` cycle, default budget three iterations. Feedback = comparable re-audit evidence; metric = the 100-point score with `unknown` and `not-applicable` categories excluded; guard = no comparable-category regression and no evidence-grade promotion; stop = target reached, budget spent, plateau, guard failure, or work that needs external credentials or a business decision. |\n| Output | `.hyper\u002Fseo\u002F[slug]\u002F` holding `results.json`, `results.js`, `dashboard.html`, `report.md`, `sources.md`, and `flow.json` for complex or optimize mode; simple and setup modes keep `report.md` and `sources.md` as the minimum. `sources.md` is a source ledger of URL, date, applicable claim, evidence class, and limitation. |\n| Verification | Apply `rules\u002Fvalidation.md` at completion: every critical or warning finding carries evidence, scores derive from observed evidence with `unknown` and `not-applicable` handled explicitly, and optimize mode records baseline, evaluator, budget, guards, discarded iterations, stop reason, and the best comparable verified result. Package changes additionally run the focused corpus validator, the repository standard gate, and the package tests. |\n| Stop condition | Stop when the requested audit or report is complete with graded evidence and no unresolved critical gap, or when optimize mode reaches its target, budget, plateau, guard, or an external dependency. Never stop by asserting a ranking, AI-feature inclusion, or citation the evidence does not support. |\n\n\u003C\u002Finstruction_contract>\n\n\u003Coutput_language>\n\nDefault all user-facing deliverables, saved artifacts, reports, plans, generated docs, summaries, handoff notes, commit\u002Fmessage drafts, and validation notes to Korean, even when this canonical skill file is written in English.\n\nPreserve source code identifiers, CLI commands, file paths, schema keys, JSON\u002FYAML field names, API names, package names, proper nouns, and quoted source excerpts in their required or original language. Use a different language only when the user explicitly requests it, an existing target artifact must stay in another language for consistency, or a machine-readable contract requires exact English tokens; when a localized template or reference exists (for example `*.ko.md` or `*.ko.json`), prefer it for user-facing artifacts.\n\n\u003C\u002Foutput_language>\n\n\u003Cpurpose>\n\n- Audit website or project SEO in a systematic way.\n- Cover on-page SEO, technical SEO, content SEO, and Core Web Vitals.\n- Evaluate AEO readiness for featured snippets, voice search, and direct-answer surfaces.\n- Evaluate GEO readiness for citation likelihood in generative AI responses.\n- Evaluate LLMO readiness for AI crawler access, freshness, and model-readable context.\n- Save prioritized recommendations and evidence under `.hyper\u002Fseo\u002F[slug]\u002F`.\n- Plan a new site or homepage launch in phases (plan, build checks, registration, first 30 days) so search engines and AI answer engines can crawl, index, and cite it.\n- Update existing reports so SEO improvement history remains traceable, and when the user asks for highest score, max score, maximum score, perfect score, or continuous improvement, run an audit to fix\u002Frecommendation to re-audit loop and keep the best result.\n\n\u003C\u002Fpurpose>\n\n\u003Crouting_rule>\n\nUse `hyper-seo` when the main outcome is an SEO\u002FAEO\u002FGEO\u002FLLMO audit, optimization report, or evidence-backed search visibility improvement plan.\n\nRoute neighboring work elsewhere:\n\n- Page or product UI design: a design deliverable, not a search-visibility audit.\n- Competitor or market research without site audit: route to the source-backed research workflow.\n- Release-gate checks whose only output is a go\u002Fno-go deployment verdict rather than a search-visibility audit: not this skill's output.\n- Pure performance engineering without search context: use the relevant performance or optimization workflow.\n- Broad AI search trend research without a target site or content set: route to the source-backed research workflow.\n\n\u003C\u002Frouting_rule>\n\n\u003Cactivation_examples>\n\nPositive examples:\n\n- \"Audit this site's SEO.\"\n- \"Check metadata and structured data.\"\n- \"Review search-engine optimization status and give improvement recommendations.\"\n- \"Optimize our content so AI search engines can cite it.\"\n- \"Check whether ChatGPT or Perplexity can surface our brand.\"\n- \"Keep iterating fixes until the SEO score is as high as possible.\"\n- \"Audit, fix, and re-verify until the search optimization score is close to perfect.\"\n- \"We are launching a new homepage next month; set up SEO, GEO, and AI crawler settings before launch.\"\n\nNegative examples:\n\n- \"Design this landing page.\" -> a page or product design deliverable, not this skill's output.\n- \"Research competitor market positioning.\" -> route to the source-backed research workflow.\n- \"Check the release checklist before deploying.\" -> a deployment gate verdict, not a search-visibility audit.\n\nBoundary examples:\n\n- \"Optimize this page's performance.\"\n  Use `hyper-seo` only when performance is evaluated through SEO\u002FCore Web Vitals impact.\n- \"Research AI search trends.\"\n  Use `hyper-seo` only when the output is tied to a target site, page, or content inventory.\n- \"Build our new homepage.\"\n  Use `hyper-seo` only for the search-visibility setup plan or checks; building the pages is not this skill's output.\n\n\u003C\u002Factivation_examples>\n\n\u003Ctrigger_conditions>\n\n| Situation | Mode |\n|------|------|\n| Full SEO audit for a new project or site | create |\n| On-page SEO review for a specific page | create |\n| Add a new analysis to an existing SEO report | update |\n| Focused Core Web Vitals or technical SEO analysis | create |\n| Re-check after SEO improvements | update |\n| Iterative improvement toward best or perfect score | optimize |\n| AEO\u002FGEO citation readiness analysis | create |\n| Add AEO\u002FGEO analysis to an existing report | update |\n| Plan or launch a new site or homepage for search and AI answer engines | setup |\n\nA request with no target site, page, or content set is not this trigger.\n\n\u003C\u002Ftrigger_conditions>\n\n\u003Cskill_architecture>\n\n- Core (`SKILL.md`): modes, intake, scoring, artifact contract, phase order, and the stop condition.\n- Rules: [rules\u002Fseo-workflow.md](rules\u002Fseo-workflow.md) owns the phases and the optimize loop; [rules\u002Fvalidation.md](rules\u002Fvalidation.md) owns the completion gates.\n- References: [references\u002Fseo-fundamentals.md](references\u002Fseo-fundamentals.md) (E-E-A-T, Core Web Vitals, schema), [references\u002Faeo-geo-guide.md](references\u002Faeo-geo-guide.md) (AEO, GEO, LLMO), [references\u002Fseo-checklist.md](references\u002Fseo-checklist.md) (scan items), [references\u002Fsite-setup.md](references\u002Fsite-setup.md) (setup mode), [references\u002Fartifact-spec.md](references\u002Fartifact-spec.md) (workspace and `results.json` schema).\n- Assets: the Korean and English report templates, the dashboard template, and `assets\u002Fevals\u002F`, the trigger and behavior cases.\n- Script: `bash scripts\u002Frender-dashboard.sh \u003Cartifact-dir>` needs Bash 3.2+ and jq; it copies the dashboard template, embeds `results.json` into `results.js`, writes `dashboard.html`, and exits non-zero naming the offending `results.json` field when the payload is structurally invalid.\n\n\u003C\u002Fskill_architecture>\n\n\u003Cloop_policy>\n\n- Only optimize mode loops; every other mode is one pass with a completion gate.\n- Record the baseline, evaluator, budget, and guards before the first change, and the stop reason when the loop ends.\n- Keep an iteration only when a comparable category improves without a regression and without promoting an evidence grade; otherwise revert it where possible or mark it `discarded`.\n- The loop procedure is [rules\u002Fseo-workflow.md](rules\u002Fseo-workflow.md) phase 9; the fields to record are in [rules\u002Fvalidation.md](rules\u002Fvalidation.md) §Optimize Mode Checks.\n\n\u003C\u002Floop_policy>\n\n\u003Clanguage_and_translation_default>\n\n- Canonical package files are English and every `*.ko.md` is a structurally aligned Korean translation; deliverables follow `\u003Coutput_language>`, with `assets\u002Freport.template.ko.md` as the default report template.\n\n\u003C\u002Flanguage_and_translation_default>\n\n\u003Creference_routing>\n\n- Read [rules\u002Fseo-workflow.md](rules\u002Fseo-workflow.md) at the start of any audit; it owns the phase procedures.\n- Read [references\u002Fseo-fundamentals.md](references\u002Fseo-fundamentals.md) when judging E-E-A-T, Core Web Vitals, ranking factors, entity signals, or schema markup.\n- Read [references\u002Faeo-geo-guide.md](references\u002Faeo-geo-guide.md) for the AEO, GEO, or LLMO dimensions, including the GEO CORE framework and `llms.txt` guidance.\n- Read [references\u002Fseo-checklist.md](references\u002Fseo-checklist.md) while scanning, for the item-by-item checks.\n- Read [references\u002Fsite-setup.md](references\u002Fsite-setup.md) only in setup mode.\n- Read [references\u002Fartifact-spec.md](references\u002Fartifact-spec.md) before writing or reviewing `.hyper\u002Fseo\u002F[slug]\u002F`, including `flow.json`.\n- Read `assets\u002Freport.template.ko.md` when drafting a report, and `assets\u002Freport.template.md` only when English is required.\n- Read `assets\u002Fdashboard-template.html` only when rendering the dashboard.\n- Read [rules\u002Fvalidation.md](rules\u002Fvalidation.md) before declaring the audit complete.\n\n\u003C\u002Freference_routing>\n\n\u003Csupport_file_read_order>\n\n1. This core, to fix the mode, the complexity, and the target.\n2. `rules\u002Fseo-workflow.md`, then `references\u002Fseo-fundamentals.md`, `references\u002Faeo-geo-guide.md`, and `references\u002Fseo-checklist.md`.\n3. `references\u002Fsite-setup.md` in setup mode, then `references\u002Fartifact-spec.md` before writing the workspace.\n4. `assets\u002Freport.template.ko.md` for the report, and [assets\u002Fdashboard-template.html](assets\u002Fdashboard-template.html) only when rendering.\n5. `rules\u002Fvalidation.md` before completion.\n\n\u003C\u002Fsupport_file_read_order>\n\n\u003Cworkflow>\n\n| Phase | Task | Output |\n|------|------|------|\n| 0 | Determine target, mode, complexity, proof surface, and universal intake fields | Execution brief |\n| 1 | Establish measurement methods and confidence limits | `measurement_methods` |\n| 2 | Collect evidence from local code, pages, browser checks, and web sources | Evidence log |\n| 3 | Audit technical SEO, platform policy, AEO, GEO, LLMO, Core Web Vitals, and structured data | Structured findings |\n| 4 | Separate official requirements from field\u002Ftool\u002Flab\u002Fsynthetic\u002Fheuristic findings | Evidence-graded findings |\n| 5 | Prioritize issues by impact, confidence, effort, and source tier | Recommendation set |\n| 6 | Write artifacts and dashboard | `.hyper\u002Fseo\u002F[slug]\u002F` |\n| 7 | If optimize mode, apply or recommend fixes and re-audit | Best verified result |\n| 8 | Summarize score, wins, confidence limits, risks, and next actions | Final report |\n\n\u003C\u002Fworkflow>\n\n\u003Ccomplexity_routing>\n\n| Complexity | Signals | Handling |\n|------|------|------|\n| **Simple** | Single-page review, one SEO element, quick metadata audit | **Direct**: write `report.md` immediately |\n| **Complex** | Full-site audit, many pages, technical SEO plus content SEO plus Core Web Vitals, competitor comparison | **Tracked**: use `flow.json` for phase tracking |\n\nBefore starting, record `Complexity: [simple\u002Fcomplex] — [one-line reason]`, `Mode: [create\u002Fupdate\u002Foptimize\u002Fsetup]`, `Target: [site\u002Fpage\u002Fproject path]`, and `Proof surface: [commands, browser checks, web sources, or local files]`.\n\n\u003C\u002Fcomplexity_routing>\n\n\u003Cuniversal_intake>\n\nBefore scoring any project, classify the audit context so this skill works across stacks:\n\n- `target_type`: `live-url`, `local-static`, `nextjs`, `react-spa`, `docs-site`, `ecommerce`, `blog`, or `app-with-marketing-pages`\n- `access_level`: live URL, local files only, Search Console available, analytics available, field Core Web Vitals available, or AI citation probe available\n- `allowed_action`: `audit-only`, `recommend`, `edit-code`, or `optimize-loop`\n- `measurement_confidence`: lower confidence when live URL, Search Console, field Core Web Vitals, or AI citation probes are unavailable\n- `evaluator`: comparable target set, scoring rubric, tools\u002Fversions, dates, and evidence channels\n\nClassify every finding and score input as exactly one of `official`, `live`, `field`, `tool`, `lab`, `synthetic`, or `heuristic`. Do not treat one class as evidence from another: a local scan is not live or field evidence, and a tool\u002Flab result is not an official requirement.\n\nRecord unavailable checks as `unknown` and irrelevant checks as `not-applicable`; exclude `not-applicable` checks from category denominators. Do not hide missing evidence. If a recommendation is based on static files, lab data, synthetic probes, or heuristics, label it that way in `results.json`.\n\nWhen live browsing, Search Console, field data, AI probes, or a named tool is unavailable, use the strongest available lower-grade method, state the capability limitation and fallback, and do not make live-performance, ranking, inclusion, or citation claims.\n\n\u003C\u002Funiversal_intake>\n\n\u003Cartifact_contract>\n\nCreate or update `.hyper\u002Fseo\u002F[slug]\u002F`.\n\nExpected files:\n\n```text\n.hyper\u002Fseo\u002F[slug]\u002F\n├── dashboard.html      # Browser-readable dashboard\n├── results.json        # Structured audit results\n├── results.js          # File URL fallback for browser rendering\n├── report.md           # Markdown report\n├── sources.md          # Source and evidence log\n└── flow.json           # Required for complex or optimize mode\n```\n\nFor simple mode, `report.md` and `sources.md` are the minimum. For complex or optimize mode, all files are expected.\n\nFollow [references\u002Fartifact-spec.md](references\u002Fartifact-spec.md) for the file schema.\n\nFor new reports, use [assets\u002Freport.template.ko.md](assets\u002Freport.template.ko.md) by default. Use [assets\u002Freport.template.md](assets\u002Freport.template.md) only when English is explicitly required.\n\nWrite `results.json` from gathered evidence first, generate `results.js` for direct local viewing, render `dashboard.html` with `bash scripts\u002Frender-dashboard.sh \u003Cartifact-dir>`, then write `report.md` and `sources.md`. `sources.md` is a source ledger: for every external or official claim, record its URL, accessed or published date, applicable claim, evidence class, and any scope\u002Favailability limitation.\n\nFor complex or optimize mode, `flow.json` tracks phases in order: `scope` → `measurement` → `technical` → `platform_policy` → `onpage` → `content` → `aeo` → `geo` → `report`.\n\n\u003C\u002Fartifact_contract>\n\n\u003Caudit_dimensions>\n\nAudit these dimensions when relevant to the target: technical SEO (crawlability, indexability, canonicalization, sitemap, robots directives, response status, redirects, duplicate pages); platform policy (Googlebot, Google-Extended, OAI-SearchBot, GPTBot, ChatGPT-User, Claude-SearchBot, ClaudeBot, PerplexityBot, and the other search, training, and user-fetch tokens as separate controls, CDN or WAF bot rules, the Search Console generative AI setting, snippet controls and X-Robots-Tag, plus the target-gated Naver and Bing\u002FIndexNow modules); on-page SEO (title, description, heading hierarchy, keyword alignment, URL readability, internal links); content SEO (intent match, depth, topical coverage, freshness, uniqueness, readability); Core Web Vitals (LCP, INP, CLS, render-blocking resources, image sizing, interaction delay); structured data (JSON-LD validity, Schema.org type fit, parity with visible content, AI trust signals); AEO (Q&A structure, direct answers, snippet readiness, voice-search phrasing); GEO\u002FLLMO (citable claims, sourced statistics, entity authority, `llms.txt`, AI crawler access, freshness).\n\nPer-dimension criteria and the conditional platform modules live in [rules\u002Fseo-workflow.md](rules\u002Fseo-workflow.md) phases 3-8, [references\u002Fseo-checklist.md](references\u002Fseo-checklist.md), [references\u002Fseo-fundamentals.md](references\u002Fseo-fundamentals.md), and [references\u002Faeo-geo-guide.md](references\u002Faeo-geo-guide.md).\n\nTwo surfaces are audited only when the target set includes them: Naver (`Yeti` crawler access, Search Advisor ownership verification, RSS and sitemap ownership-domain match, `og:image` conditions, `nosourceinfo` scope) and Bing (IndexNow change notification, a receipt code that is never index or citation evidence, key-file ownership proof, the per-POST submission limit, sitemap field handling).\n\nTreat character counts, heading counts, link density, answer length, word counts, and platform content preferences as context-dependent heuristics. Evaluate Google AI features through ordinary SEO fundamentals without prescribing special AI schema or text files.\n\n\u003C\u002Faudit_dimensions>\n\n\u003Cscoring>\n\nUse a transparent 100-point score when enough evidence exists:\n\n- Technical SEO: 20\n- On-page SEO: 20\n- Content SEO: 15\n- Core Web Vitals: 15\n- Structured data: 10\n- AEO readiness: 10\n- GEO\u002FLLMO readiness: 10\n\nIf evidence is incomplete, mark affected categories as `unknown`; mark irrelevant categories as `not-applicable` and exclude them from the score denominator.\n\nEach finding carries severity (`critical`, `warning`, `info`), confidence, `evidence_grade` (`official`, `live`, `field`, `tool`, `lab`, `synthetic`, `heuristic`), `measurement_method`, `source_tier`, the evidence itself, a specific recommendation with its expected impact, and the owner surface (code, content, infrastructure, analytics, external platform). [references\u002Fartifact-spec.md](references\u002Fartifact-spec.md) holds the allowed values and the schema.\n\n\u003C\u002Fscoring>\n\n\u003Crequired>\n\n| Category | Required |\n|---|---|\n| Target | A named target, and the mode, complexity, and proof surface recorded before scoring |\n| Evidence | Every critical and warning finding carries a command, URL, file path, or probe result, plus its evidence grade and source tier |\n| Scoring | A total computed only from observed categories, with `unknown` and `not-applicable` excluded rather than assumed |\n| Output | The artifact set `\u003Cartifact_contract>` requires for the chosen mode |\n| Limits | A missing channel named as a capability limit with its fallback, never papered over |\n\n\u003C\u002Frequired>\n\n\u003Cforbidden>\n\n| Category | Forbidden |\n|---|---|\n| Evidence | A score, ranking, inclusion, or citation asserted without a recorded measurement; an `unknown` filled in to make a total |\n| Grading | A heuristic presented as an official pass\u002Ffail requirement; a tool, lab, or synthetic result promoted to an official requirement |\n| Guarantees | Implying that structured data, `llms.txt`, or index and snippet eligibility guarantees rich results, ranking, AI inclusion, or a citation; promising a perfect score |\n| Scope | Editing outside the audited target, or taking an account action that needs the owner's credentials without permission |\n| Claims | A live-performance, ranking, or citation claim made while the channel that would prove it was unavailable |\n\n\u003C\u002Fforbidden>\n\n\u003Cvalidation>\n\nApply [rules\u002Fvalidation.md](rules\u002Fvalidation.md) before declaring an audit complete. It requires evidence on every critical and warning finding; recommendations specific enough for an engineer, marketer, or content owner to act on; scores derived from observed evidence with `unknown` and `not-applicable` handled explicitly rather than assumed; Google AI features described through ordinary SEO fundamentals, with FAQPage recommendations that separate Google rich-result eligibility from answer-friendly visible FAQ content; a `sources.md` source ledger carrying URL, date, applicable claim, evidence class, and limitations; and, in optimize mode, the recorded baseline, evaluator, finite budget, guards, changes and recommendations, re-audit evidence, discarded iterations, and stop reason.\n\nThe artifacts that must remain are listed in `\u003Cartifact_contract>`.\n\n\u003C\u002Fvalidation>\n\n## Sources\n\n> Checked 2026-11-09. The mode set, the 100-point weights, and the optimize guards are this package's design (user instruction, 2026-08-20) and are restated in [rules\u002Fseo-workflow.md](rules\u002Fseo-workflow.md); every external fact the audit applies carries its own date in the reference that states it, and the package shape follows `instructions\u002Fskill\u002FSKILL_AUTHORING.md`.\n","@rules\u002Fseo-workflow.md\n@rules\u002Fvalidation.md\n\n# Hyper SEO\n\n> Audit and improve a project's search visibility across traditional search engines and AI answer engines.\n\n\u003Cinstruction_contract>\n\n| Field | Contract |\n|---|---|\n| Intent | Produce an evidence-graded SEO\u002FAEO\u002FGEO\u002FLLMO audit and a prioritized, actionable optimization report for a named target, produce a phased setup plan when a site or homepage is being planned or launched, and drive a bounded score-improvement loop when the user asks for the best achievable score. |\n| Scope | Owns target classification, measurement-method selection, on-page\u002Ftechnical\u002Fcontent\u002FCore Web Vitals\u002FAEO\u002FGEO\u002FLLMO assessment, new-site setup planning, scoring, findings, recommendations, and the report workspace. Does not own implementation outside the audited target, release gating, page or product design, account actions that need the owner's credentials unless permitted, or broad market research that has no target site or content set. |\n| Authority | System\u002Fharness and user instructions > the audited target's own files and live observations > official platform documentation > this skill > heuristic preference. A tool, lab, synthetic, or heuristic observation is never promoted to an official requirement. |\n| Evidence | Read the target's own files, rendered pages, and live responses before scoring, and cite the command, URL, file path, or probe result behind every critical and warning finding. Record unavailable checks as `unknown` and irrelevant checks as `not-applicable`; never invent a score, a ranking, an inclusion, or a citation. |\n| Tools | Use available read\u002Fsearch\u002Fbrowser tools, and render the dashboard with `bash scripts\u002Frender-dashboard.sh \u003Cartifact-dir>`. Web search, browser inspection, field Core Web Vitals, Search Console, or an AI citation probe are used only when actually available; when one is missing, state the capability limit and fall back to the strongest lower-grade method. |\n| Loop | Optimize mode only: a bounded `audit -> fix or recommendation -> re-audit` cycle, default budget three iterations. Feedback = comparable re-audit evidence; metric = the 100-point score with `unknown` and `not-applicable` categories excluded; guard = no comparable-category regression and no evidence-grade promotion; stop = target reached, budget spent, plateau, guard failure, or work that needs external credentials or a business decision. |\n| Output | `.hyper\u002Fseo\u002F[slug]\u002F` holding `results.json`, `results.js`, `dashboard.html`, `report.md`, `sources.md`, and `flow.json` for complex or optimize mode; simple and setup modes keep `report.md` and `sources.md` as the minimum. `sources.md` is a source ledger of URL, date, applicable claim, evidence class, and limitation. |\n| Verification | Apply `rules\u002Fvalidation.md` at completion: every critical or warning finding carries evidence, scores derive from observed evidence with `unknown` and `not-applicable` handled explicitly, and optimize mode records baseline, evaluator, budget, guards, discarded iterations, stop reason, and the best comparable verified result. Package changes additionally run the focused corpus validator, the repository standard gate, and the package tests. |\n| Stop condition | Stop when the requested audit or report is complete with graded evidence and no unresolved critical gap, or when optimize mode reaches its target, budget, plateau, guard, or an external dependency. Never stop by asserting a ranking, AI-feature inclusion, or citation the evidence does not support. |\n\n\u003C\u002Finstruction_contract>\n\n\u003Coutput_language>\n\nDefault all user-facing deliverables, saved artifacts, reports, plans, generated docs, summaries, handoff notes, commit\u002Fmessage drafts, and validation notes to Korean, even when this canonical skill file is written in English.\n\nPreserve source code identifiers, CLI commands, file paths, schema keys, JSON\u002FYAML field names, API names, package names, proper nouns, and quoted source excerpts in their required or original language. Use a different language only when the user explicitly requests it, an existing target artifact must stay in another language for consistency, or a machine-readable contract requires exact English tokens; when a localized template or reference exists (for example `*.ko.md` or `*.ko.json`), prefer it for user-facing artifacts.\n\n\u003C\u002Foutput_language>\n\n\u003Cpurpose>\n\n- Audit website or project SEO in a systematic way.\n- Cover on-page SEO, technical SEO, content SEO, and Core Web Vitals.\n- Evaluate AEO readiness for featured snippets, voice search, and direct-answer surfaces.\n- Evaluate GEO readiness for citation likelihood in generative AI responses.\n- Evaluate LLMO readiness for AI crawler access, freshness, and model-readable context.\n- Save prioritized recommendations and evidence under `.hyper\u002Fseo\u002F[slug]\u002F`.\n- Plan a new site or homepage launch in phases (plan, build checks, registration, first 30 days) so search engines and AI answer engines can crawl, index, and cite it.\n- Update existing reports so SEO improvement history remains traceable, and when the user asks for highest score, max score, maximum score, perfect score, or continuous improvement, run an audit to fix\u002Frecommendation to re-audit loop and keep the best result.\n\n\u003C\u002Fpurpose>\n\n\u003Crouting_rule>\n\nUse `hyper-seo` when the main outcome is an SEO\u002FAEO\u002FGEO\u002FLLMO audit, optimization report, or evidence-backed search visibility improvement plan.\n\nRoute neighboring work elsewhere:\n\n- Page or product UI design: a design deliverable, not a search-visibility audit.\n- Competitor or market research without site audit: route to the source-backed research workflow.\n- Release-gate checks whose only output is a go\u002Fno-go deployment verdict rather than a search-visibility audit: not this skill's output.\n- Pure performance engineering without search context: use the relevant performance or optimization workflow.\n- Broad AI search trend research without a target site or content set: route to the source-backed research workflow.\n\n\u003C\u002Frouting_rule>\n\n\u003Cactivation_examples>\n\nPositive examples:\n\n- \"Audit this site's SEO.\"\n- \"Check metadata and structured data.\"\n- \"Review search-engine optimization status and give improvement recommendations.\"\n- \"Optimize our content so AI search engines can cite it.\"\n- \"Check whether ChatGPT or Perplexity can surface our brand.\"\n- \"Keep iterating fixes until the SEO score is as high as possible.\"\n- \"Audit, fix, and re-verify until the search optimization score is close to perfect.\"\n- \"We are launching a new homepage next month; set up SEO, GEO, and AI crawler settings before launch.\"\n\nNegative examples:\n\n- \"Design this landing page.\" -> a page or product design deliverable, not this skill's output.\n- \"Research competitor market positioning.\" -> route to the source-backed research workflow.\n- \"Check the release checklist before deploying.\" -> a deployment gate verdict, not a search-visibility audit.\n\nBoundary examples:\n\n- \"Optimize this page's performance.\"\n  Use `hyper-seo` only when performance is evaluated through SEO\u002FCore Web Vitals impact.\n- \"Research AI search trends.\"\n  Use `hyper-seo` only when the output is tied to a target site, page, or content inventory.\n- \"Build our new homepage.\"\n  Use `hyper-seo` only for the search-visibility setup plan or checks; building the pages is not this skill's output.\n\n\u003C\u002Factivation_examples>\n\n\u003Ctrigger_conditions>\n\n| Situation | Mode |\n|------|------|\n| Full SEO audit for a new project or site | create |\n| On-page SEO review for a specific page | create |\n| Add a new analysis to an existing SEO report | update |\n| Focused Core Web Vitals or technical SEO analysis | create |\n| Re-check after SEO improvements | update |\n| Iterative improvement toward best or perfect score | optimize |\n| AEO\u002FGEO citation readiness analysis | create |\n| Add AEO\u002FGEO analysis to an existing report | update |\n| Plan or launch a new site or homepage for search and AI answer engines | setup |\n\nA request with no target site, page, or content set is not this trigger.\n\n\u003C\u002Ftrigger_conditions>\n\n\u003Cskill_architecture>\n\n- Core (`SKILL.md`): modes, intake, scoring, artifact contract, phase order, and the stop condition.\n- Rules: [rules\u002Fseo-workflow.md](rules\u002Fseo-workflow.md) owns the phases and the optimize loop; [rules\u002Fvalidation.md](rules\u002Fvalidation.md) owns the completion gates.\n- References: [references\u002Fseo-fundamentals.md](references\u002Fseo-fundamentals.md) (E-E-A-T, Core Web Vitals, schema), [references\u002Faeo-geo-guide.md](references\u002Faeo-geo-guide.md) (AEO, GEO, LLMO), [references\u002Fseo-checklist.md](references\u002Fseo-checklist.md) (scan items), [references\u002Fsite-setup.md](references\u002Fsite-setup.md) (setup mode), [references\u002Fartifact-spec.md](references\u002Fartifact-spec.md) (workspace and `results.json` schema).\n- Assets: the Korean and English report templates, the dashboard template, and `assets\u002Fevals\u002F`, the trigger and behavior cases.\n- Script: `bash scripts\u002Frender-dashboard.sh \u003Cartifact-dir>` needs Bash 3.2+ and jq; it copies the dashboard template, embeds `results.json` into `results.js`, writes `dashboard.html`, and exits non-zero naming the offending `results.json` field when the payload is structurally invalid.\n\n\u003C\u002Fskill_architecture>\n\n\u003Cloop_policy>\n\n- Only optimize mode loops; every other mode is one pass with a completion gate.\n- Record the baseline, evaluator, budget, and guards before the first change, and the stop reason when the loop ends.\n- Keep an iteration only when a comparable category improves without a regression and without promoting an evidence grade; otherwise revert it where possible or mark it `discarded`.\n- The loop procedure is [rules\u002Fseo-workflow.md](rules\u002Fseo-workflow.md) phase 9; the fields to record are in [rules\u002Fvalidation.md](rules\u002Fvalidation.md) §Optimize Mode Checks.\n\n\u003C\u002Floop_policy>\n\n\u003Clanguage_and_translation_default>\n\n- Canonical package files are English and every `*.ko.md` is a structurally aligned Korean translation; deliverables follow `\u003Coutput_language>`, with `assets\u002Freport.template.ko.md` as the default report template.\n\n\u003C\u002Flanguage_and_translation_default>\n\n\u003Creference_routing>\n\n- Read [rules\u002Fseo-workflow.md](rules\u002Fseo-workflow.md) at the start of any audit; it owns the phase procedures.\n- Read [references\u002Fseo-fundamentals.md](references\u002Fseo-fundamentals.md) when judging E-E-A-T, Core Web Vitals, ranking factors, entity signals, or schema markup.\n- Read [references\u002Faeo-geo-guide.md](references\u002Faeo-geo-guide.md) for the AEO, GEO, or LLMO dimensions, including the GEO CORE framework and `llms.txt` guidance.\n- Read [references\u002Fseo-checklist.md](references\u002Fseo-checklist.md) while scanning, for the item-by-item checks.\n- Read [references\u002Fsite-setup.md](references\u002Fsite-setup.md) only in setup mode.\n- Read [references\u002Fartifact-spec.md](references\u002Fartifact-spec.md) before writing or reviewing `.hyper\u002Fseo\u002F[slug]\u002F`, including `flow.json`.\n- Read `assets\u002Freport.template.ko.md` when drafting a report, and `assets\u002Freport.template.md` only when English is required.\n- Read `assets\u002Fdashboard-template.html` only when rendering the dashboard.\n- Read [rules\u002Fvalidation.md](rules\u002Fvalidation.md) before declaring the audit complete.\n\n\u003C\u002Freference_routing>\n\n\u003Csupport_file_read_order>\n\n1. This core, to fix the mode, the complexity, and the target.\n2. `rules\u002Fseo-workflow.md`, then `references\u002Fseo-fundamentals.md`, `references\u002Faeo-geo-guide.md`, and `references\u002Fseo-checklist.md`.\n3. `references\u002Fsite-setup.md` in setup mode, then `references\u002Fartifact-spec.md` before writing the workspace.\n4. `assets\u002Freport.template.ko.md` for the report, and [assets\u002Fdashboard-template.html](assets\u002Fdashboard-template.html) only when rendering.\n5. `rules\u002Fvalidation.md` before completion.\n\n\u003C\u002Fsupport_file_read_order>\n\n\u003Cworkflow>\n\n| Phase | Task | Output |\n|------|------|------|\n| 0 | Determine target, mode, complexity, proof surface, and universal intake fields | Execution brief |\n| 1 | Establish measurement methods and confidence limits | `measurement_methods` |\n| 2 | Collect evidence from local code, pages, browser checks, and web sources | Evidence log |\n| 3 | Audit technical SEO, platform policy, AEO, GEO, LLMO, Core Web Vitals, and structured data | Structured findings |\n| 4 | Separate official requirements from field\u002Ftool\u002Flab\u002Fsynthetic\u002Fheuristic findings | Evidence-graded findings |\n| 5 | Prioritize issues by impact, confidence, effort, and source tier | Recommendation set |\n| 6 | Write artifacts and dashboard | `.hyper\u002Fseo\u002F[slug]\u002F` |\n| 7 | If optimize mode, apply or recommend fixes and re-audit | Best verified result |\n| 8 | Summarize score, wins, confidence limits, risks, and next actions | Final report |\n\n\u003C\u002Fworkflow>\n\n\u003Ccomplexity_routing>\n\n| Complexity | Signals | Handling |\n|------|------|------|\n| **Simple** | Single-page review, one SEO element, quick metadata audit | **Direct**: write `report.md` immediately |\n| **Complex** | Full-site audit, many pages, technical SEO plus content SEO plus Core Web Vitals, competitor comparison | **Tracked**: use `flow.json` for phase tracking |\n\nBefore starting, record `Complexity: [simple\u002Fcomplex] — [one-line reason]`, `Mode: [create\u002Fupdate\u002Foptimize\u002Fsetup]`, `Target: [site\u002Fpage\u002Fproject path]`, and `Proof surface: [commands, browser checks, web sources, or local files]`.\n\n\u003C\u002Fcomplexity_routing>\n\n\u003Cuniversal_intake>\n\nBefore scoring any project, classify the audit context so this skill works across stacks:\n\n- `target_type`: `live-url`, `local-static`, `nextjs`, `react-spa`, `docs-site`, `ecommerce`, `blog`, or `app-with-marketing-pages`\n- `access_level`: live URL, local files only, Search Console available, analytics available, field Core Web Vitals available, or AI citation probe available\n- `allowed_action`: `audit-only`, `recommend`, `edit-code`, or `optimize-loop`\n- `measurement_confidence`: lower confidence when live URL, Search Console, field Core Web Vitals, or AI citation probes are unavailable\n- `evaluator`: comparable target set, scoring rubric, tools\u002Fversions, dates, and evidence channels\n\nClassify every finding and score input as exactly one of `official`, `live`, `field`, `tool`, `lab`, `synthetic`, or `heuristic`. Do not treat one class as evidence from another: a local scan is not live or field evidence, and a tool\u002Flab result is not an official requirement.\n\nRecord unavailable checks as `unknown` and irrelevant checks as `not-applicable`; exclude `not-applicable` checks from category denominators. Do not hide missing evidence. If a recommendation is based on static files, lab data, synthetic probes, or heuristics, label it that way in `results.json`.\n\nWhen live browsing, Search Console, field data, AI probes, or a named tool is unavailable, use the strongest available lower-grade method, state the capability limitation and fallback, and do not make live-performance, ranking, inclusion, or citation claims.\n\n\u003C\u002Funiversal_intake>\n\n\u003Cartifact_contract>\n\nCreate or update `.hyper\u002Fseo\u002F[slug]\u002F`.\n\nExpected files:\n\n```text\n.hyper\u002Fseo\u002F[slug]\u002F\n├── dashboard.html      # Browser-readable dashboard\n├── results.json        # Structured audit results\n├── results.js          # File URL fallback for browser rendering\n├── report.md           # Markdown report\n├── sources.md          # Source and evidence log\n└── flow.json           # Required for complex or optimize mode\n```\n\nFor simple mode, `report.md` and `sources.md` are the minimum. For complex or optimize mode, all files are expected.\n\nFollow [references\u002Fartifact-spec.md](references\u002Fartifact-spec.md) for the file schema.\n\nFor new reports, use [assets\u002Freport.template.ko.md](assets\u002Freport.template.ko.md) by default. Use [assets\u002Freport.template.md](assets\u002Freport.template.md) only when English is explicitly required.\n\nWrite `results.json` from gathered evidence first, generate `results.js` for direct local viewing, render `dashboard.html` with `bash scripts\u002Frender-dashboard.sh \u003Cartifact-dir>`, then write `report.md` and `sources.md`. `sources.md` is a source ledger: for every external or official claim, record its URL, accessed or published date, applicable claim, evidence class, and any scope\u002Favailability limitation.\n\nFor complex or optimize mode, `flow.json` tracks phases in order: `scope` → `measurement` → `technical` → `platform_policy` → `onpage` → `content` → `aeo` → `geo` → `report`.\n\n\u003C\u002Fartifact_contract>\n\n\u003Caudit_dimensions>\n\nAudit these dimensions when relevant to the target: technical SEO (crawlability, indexability, canonicalization, sitemap, robots directives, response status, redirects, duplicate pages); platform policy (Googlebot, Google-Extended, OAI-SearchBot, GPTBot, ChatGPT-User, Claude-SearchBot, ClaudeBot, PerplexityBot, and the other search, training, and user-fetch tokens as separate controls, CDN or WAF bot rules, the Search Console generative AI setting, snippet controls and X-Robots-Tag, plus the target-gated Naver and Bing\u002FIndexNow modules); on-page SEO (title, description, heading hierarchy, keyword alignment, URL readability, internal links); content SEO (intent match, depth, topical coverage, freshness, uniqueness, readability); Core Web Vitals (LCP, INP, CLS, render-blocking resources, image sizing, interaction delay); structured data (JSON-LD validity, Schema.org type fit, parity with visible content, AI trust signals); AEO (Q&A structure, direct answers, snippet readiness, voice-search phrasing); GEO\u002FLLMO (citable claims, sourced statistics, entity authority, `llms.txt`, AI crawler access, freshness).\n\nPer-dimension criteria and the conditional platform modules live in [rules\u002Fseo-workflow.md](rules\u002Fseo-workflow.md) phases 3-8, [references\u002Fseo-checklist.md](references\u002Fseo-checklist.md), [references\u002Fseo-fundamentals.md](references\u002Fseo-fundamentals.md), and [references\u002Faeo-geo-guide.md](references\u002Faeo-geo-guide.md).\n\nTwo surfaces are audited only when the target set includes them: Naver (`Yeti` crawler access, Search Advisor ownership verification, RSS and sitemap ownership-domain match, `og:image` conditions, `nosourceinfo` scope) and Bing (IndexNow change notification, a receipt code that is never index or citation evidence, key-file ownership proof, the per-POST submission limit, sitemap field handling).\n\nTreat character counts, heading counts, link density, answer length, word counts, and platform content preferences as context-dependent heuristics. Evaluate Google AI features through ordinary SEO fundamentals without prescribing special AI schema or text files.\n\n\u003C\u002Faudit_dimensions>\n\n\u003Cscoring>\n\nUse a transparent 100-point score when enough evidence exists:\n\n- Technical SEO: 20\n- On-page SEO: 20\n- Content SEO: 15\n- Core Web Vitals: 15\n- Structured data: 10\n- AEO readiness: 10\n- GEO\u002FLLMO readiness: 10\n\nIf evidence is incomplete, mark affected categories as `unknown`; mark irrelevant categories as `not-applicable` and exclude them from the score denominator.\n\nEach finding carries severity (`critical`, `warning`, `info`), confidence, `evidence_grade` (`official`, `live`, `field`, `tool`, `lab`, `synthetic`, `heuristic`), `measurement_method`, `source_tier`, the evidence itself, a specific recommendation with its expected impact, and the owner surface (code, content, infrastructure, analytics, external platform). [references\u002Fartifact-spec.md](references\u002Fartifact-spec.md) holds the allowed values and the schema.\n\n\u003C\u002Fscoring>\n\n\u003Crequired>\n\n| Category | Required |\n|---|---|\n| Target | A named target, and the mode, complexity, and proof surface recorded before scoring |\n| Evidence | Every critical and warning finding carries a command, URL, file path, or probe result, plus its evidence grade and source tier |\n| Scoring | A total computed only from observed categories, with `unknown` and `not-applicable` excluded rather than assumed |\n| Output | The artifact set `\u003Cartifact_contract>` requires for the chosen mode |\n| Limits | A missing channel named as a capability limit with its fallback, never papered over |\n\n\u003C\u002Frequired>\n\n\u003Cforbidden>\n\n| Category | Forbidden |\n|---|---|\n| Evidence | A score, ranking, inclusion, or citation asserted without a recorded measurement; an `unknown` filled in to make a total |\n| Grading | A heuristic presented as an official pass\u002Ffail requirement; a tool, lab, or synthetic result promoted to an official requirement |\n| Guarantees | Implying that structured data, `llms.txt`, or index and snippet eligibility guarantees rich results, ranking, AI inclusion, or a citation; promising a perfect score |\n| Scope | Editing outside the audited target, or taking an account action that needs the owner's credentials without permission |\n| Claims | A live-performance, ranking, or citation claim made while the channel that would prove it was unavailable |\n\n\u003C\u002Fforbidden>\n\n\u003Cvalidation>\n\nApply [rules\u002Fvalidation.md](rules\u002Fvalidation.md) before declaring an audit complete. It requires evidence on every critical and warning finding; recommendations specific enough for an engineer, marketer, or content owner to act on; scores derived from observed evidence with `unknown` and `not-applicable` handled explicitly rather than assumed; Google AI features described through ordinary SEO fundamentals, with FAQPage recommendations that separate Google rich-result eligibility from answer-friendly visible FAQ content; a `sources.md` source ledger carrying URL, date, applicable claim, evidence class, and limitations; and, in optimize mode, the recorded baseline, evaluator, finite budget, guards, changes and recommendations, re-audit evidence, discarded iterations, and stop reason.\n\nThe artifacts that must remain are listed in `\u003Cartifact_contract>`.\n\n\u003C\u002Fvalidation>\n\n## Sources\n\n> Checked 2026-11-09. The mode set, the 100-point weights, and the optimize guards are this package's design (user instruction, 2026-08-20) and are restated in [rules\u002Fseo-workflow.md](rules\u002Fseo-workflow.md); every external fact the audit applies carries its own date in the reference that states it, and the package shape follows `instructions\u002Fskill\u002FSKILL_AUTHORING.md`.\n",{"name":5,"description":7,"compatibility":57},"Works best with live web access, browser inspection, local source search, Lighthouse or Core Web Vitals data when available, and read\u002Fwrite access for report artifacts.","main","f620abaff09061f8c8b1f1559dca3fdd031a32e5","plugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill hyper-seo",{"tool":74,"command":75},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill hyper-seo",{"tool":77,"command":78},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill hyper-seo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002FSKILL.md",true,[82,88,92,96,100,104,110,114,118,122,126,130,134,138,142,146,150,154,158,162,168],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"assets\u002Fdashboard-template.html","ASSET","资产文件",19766,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002Fassets\u002Fdashboard-template.html",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"assets\u002Fevals\u002Fhyper-seo-cases.jsonl",21114,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002Fassets\u002Fevals\u002Fhyper-seo-cases.jsonl",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"assets\u002Fevals\u002Fhyper-seo-cases.ko.jsonl",21786,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002Fassets\u002Fevals\u002Fhyper-seo-cases.ko.jsonl",{"path":97,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":98,"sourceHtmlUrl":99},"assets\u002Freport.template.ko.md",9865,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002Fassets\u002Freport.template.ko.md",{"path":101,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":102,"sourceHtmlUrl":103},"assets\u002Freport.template.md",10263,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002Fassets\u002Freport.template.md",{"path":105,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Faeo-geo-guide.ko.md","REFERENCE","参考文档",21849,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002Freferences\u002Faeo-geo-guide.ko.md",{"path":111,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Faeo-geo-guide.md",20814,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002Freferences\u002Faeo-geo-guide.md",{"path":115,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002Fartifact-spec.ko.md",15950,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002Freferences\u002Fartifact-spec.ko.md",{"path":119,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Fartifact-spec.md",15248,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002Freferences\u002Fartifact-spec.md",{"path":123,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fseo-checklist.ko.md",15437,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002Freferences\u002Fseo-checklist.ko.md",{"path":127,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fseo-checklist.md",14576,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002Freferences\u002Fseo-checklist.md",{"path":131,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Fseo-fundamentals.ko.md",20679,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002Freferences\u002Fseo-fundamentals.ko.md",{"path":135,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Fseo-fundamentals.md",19392,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002Freferences\u002Fseo-fundamentals.md",{"path":139,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":140,"sourceHtmlUrl":141},"references\u002Fsite-setup.ko.md",14680,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002Freferences\u002Fsite-setup.ko.md",{"path":143,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":144,"sourceHtmlUrl":145},"references\u002Fsite-setup.md",13318,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002Freferences\u002Fsite-setup.md",{"path":147,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":148,"sourceHtmlUrl":149},"rules\u002Fseo-workflow.ko.md",20948,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002Frules\u002Fseo-workflow.ko.md",{"path":151,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":152,"sourceHtmlUrl":153},"rules\u002Fseo-workflow.md",19227,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002Frules\u002Fseo-workflow.md",{"path":155,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":156,"sourceHtmlUrl":157},"rules\u002Fvalidation.ko.md",8946,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002Frules\u002Fvalidation.ko.md",{"path":159,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":160,"sourceHtmlUrl":161},"rules\u002Fvalidation.md",8481,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002Frules\u002Fvalidation.md",{"path":163,"resourceType":164,"resourceTypeDesc":165,"sizeBytes":166,"sourceHtmlUrl":167},"scripts\u002Frender-dashboard.sh","SCRIPT","脚本",21341,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002Fscripts\u002Frender-dashboard.sh",{"path":169,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":170,"sourceHtmlUrl":171},"SKILL.ko.md",24409,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Falpoxdev\u002Fhypercore\u002Fskills\u002Fhyper-seo\u002FSKILL.ko.md",[173,183,191,199,207,215],{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":177,"licenseFileUrl":178,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":182},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":177,"licenseFileUrl":187,"sourceHtmlUrl":188,"categories":189,"keywords":190,"publishedAt":182},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":177,"licenseFileUrl":195,"sourceHtmlUrl":196,"categories":197,"keywords":198,"publishedAt":182},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":177,"licenseFileUrl":203,"sourceHtmlUrl":204,"categories":205,"keywords":206,"publishedAt":182},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":177,"licenseFileUrl":211,"sourceHtmlUrl":212,"categories":213,"keywords":214,"publishedAt":182},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":177,"licenseFileUrl":219,"sourceHtmlUrl":220,"categories":221,"keywords":222,"publishedAt":182},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]