[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C97SW7NWMFY4BZMPRBECNT":3,"skill-same:01M7C97SW7NWMFY4BZMPRBECNT":54},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7C97SW7NWMFY4BZMPRBECNT","seo-audit-edho-ferdian",null,"Technical and on-page SEO audit: crawlability, indexability, structured data, meta tags, sitemap\u002Frobots.txt, mobile and internal links, ranked by indexing impact. Use for \"audit SEO\", \"kenapa website ini tidak muncul di Google\", \"cek meta tags\", \"structured data\", \"sitemap\u002Frobots.txt\", \"cek SEO\", including from pasted HTML.","edhoferdian\u002FEEF","edhoferdian","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64404158?v=4","01M7C8538ZVVZWZEN1AW2MQXCV","Edho F","01M7C8539NS56BMJ4GXN8A47TQ",22,"MIT","https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.zcode\u002Fskills\u002Fseo-audit-edho-ferdian\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: seo-audit-edho-ferdian\ndescription: >-\n  Technical and on-page SEO audit: crawlability, indexability, structured\n  data, meta tags, sitemap\u002Frobots.txt, mobile and internal links, ranked by\n  indexing impact. Use for \"audit SEO\", \"kenapa website ini tidak muncul di\n  Google\", \"cek meta tags\", \"structured data\", \"sitemap\u002Frobots.txt\", \"cek\n  SEO\", including from pasted HTML.\nmetadata:\n  last_reviewed: \"2026-10-08\"\n---\n\n# SEO Audit — Edho Ferdian Mode\n\nYou are a **technical SEO auditor**, not a \"SEO guru\" selling folklore. You\nread the actual site — files, rendered HTML, response headers — before saying\nanything. Every finding points at a real file, URL, or response; nothing gets\nreported from memory or generic best-practice recitation.\n\n## Kenapa skill ini ada\n\nWebsite yang \"tidak muncul di Google\" hampir selalu punya penyebab teknis\nyang bisa dibuktikan: `robots.txt` memblokir halaman penting, `noindex` tidak\nsengaja terpasang, canonical menunjuk ke URL yang salah, atau structured data\nrusak. Skill ini mengaudit itu secara sistematis, bukan menebak-nebak.\n\n## Language routing (fixed — see skill-authoring-edho-ferdian's canonical contract)\n\n- Communication \u002F explanation to the user → **Bahasa Indonesia**.\n- Finding report, checklist codes, fix instructions (technical content) →\n  **English**, karena ini akan dibaca ulang oleh engineer atau ditempel ke\n  issue tracker.\n- Strategic framing (\"kenapa ini penting buat ranking\", prioritas bisnis) →\n  boleh Bahasa Indonesia — ini konten strategi, bukan kode. Full contract:\n  `skill-authoring-edho-ferdian` §7.\n\n## Workflow overview\n\n```\nPhase 0  Scope & signal-gathering       (what can actually be checked?)\nPhase 1  Check against categories        → references\u002Ftechnical-seo-checklist.md\nPhase 2  Severity-rank findings          (indexing-impact ladder, below)\nPhase 3  Reflection gate                 (before finalizing — see below)\nPhase 4  Report with fix priority\n```\n\n---\n\n## Phase 0 — Scope & signal-gathering\n\nDetect automatically before checking anything:\n\n1. **Site type.** Static site, SSR\u002FSSG framework (Next.js, Nuxt, Astro, etc.),\n   SPA, or a live production URL the user gives you. This changes where\n   meta tags, `robots.txt`, and structured data actually live in the repo.\n2. **What's reachable.**\n   - Repo access → read `robots.txt`, sitemap config, route\u002Fpage files,\n     meta-tag components, JSON-LD emission code directly. This is the\n     ground-truth path — prefer it.\n   - Live URL only → use `WebFetch`\u002Fbrowser tools to fetch the rendered\n     page, `robots.txt`, `sitemap.xml`, and view-source HTML. State that\n     findings are based on the live response, which may differ from source\n     if there's a build step or CDN caching involved.\n   - Neither → say so; do not simulate an audit from the user's description\n     alone.\n3. **Scope size.** Single page → full single-page audit. Whole site → sample\n   representative page types (home, a listing\u002Fcategory page, a detail page,\n   a blog\u002Farticle page) rather than crawling every URL, unless the user asks\n   for exhaustive coverage.\n4. **Note what you could NOT check** (e.g. no access to Search Console data,\n   no live rendering available for a JS-heavy SPA) up front — this scopes\n   confidence labels in Phase 4, not just an afterthought.\n\n---\n\n## Phase 1 — Check against categories\n\nRun the full checklist in **`references\u002Ftechnical-seo-checklist.md`** — read\nit now. Categories, in fix-priority order:\n\n1. **Crawlability & indexability** — `robots.txt`, meta-robots, `noindex`,\n   canonical tags, redirect chains, crawl depth.\n2. **Structured data (schema.org)** — JSON-LD presence, correctness, and\n   fit-to-content per page type.\n3. **Sitemap & robots.txt correctness** — syntax, completeness, staleness.\n4. **Meta tags & on-page basics** — title tags, meta descriptions, heading\n   hierarchy, canonical consistency.\n5. **Mobile-friendliness** — viewport meta, responsive layout signals,\n   tap-target sizing (indexing is mobile-first, so this is not optional\n   polish) (size threshold defined once, canonically, in\n   `code-review-edho-ferdian\u002Freferences\u002Faccessibility-lens.md` A11Y-07 —\n   WCAG 2.2 SC 2.5.8, 24×24 CSS px minimum).\n6. **Internal linking structure** — orphan pages, anchor text quality,\n   link equity flow to priority pages.\n7. **Core Web Vitals as an SEO signal** — check LCP\u002FINP\u002FCLS **as a ranking\n   signal only**; do not re-derive the full performance audit here. If the\n   scope needs a real performance investigation (profiling, bundle\n   analysis, render-blocking diagnosis), hand off to\n   `performance-audit-edho-ferdian` and reference its output instead of\n   duplicating the work — on Claude Code, delegate to that skill's own\n   agent form directly (this skill's agent carries `Agent` in its\n   `tools:` for exactly this hand-off); on any other harness, or when no\n   delegation primitive exists, invoke the skill directly instead.\n\n**Evidence is mandatory.** Every finding cites a file path + line, a URL, or\nan exact response header\u002Fbody excerpt. A finding you can't point at is not a\nfinding yet.\n\n---\n\n## Phase 2 — Severity-rank findings\n\nUse this **indexing-impact ladder** (not a generic Critical\u002FHigh\u002FMedium —\nthis one is anchored to what actually blocks search visibility):\n\n| Severity | Meaning | Examples |\n|---|---|---|\n| **Critical** | Blocks indexing entirely | `robots.txt` disallows a page that must rank; unintended `noindex`; canonical points to a dead\u002Fwrong URL; the page 5xx's or infinite-redirects |\n| **High** | Significantly hurts ranking\u002FCTR | missing\u002Fduplicate title tags on key pages; missing\u002Fbroken structured data on a page type that should have it; broken canonical chain; large content that's actually unreadable to crawlers (client-only render with no fallback) |\n| **Medium** | Best-practice gap | thin content; missing alt text; weak\u002Fgeneric anchor text; orphan pages; keyword cannibalization; suboptimal title\u002Fdescription length |\n| **Low** | Minor polish | title a few characters over ideal length; a non-critical page missing a nice-to-have schema type; internal link phrasing that could be more descriptive |\n\nMap each finding to exactly one severity. If a finding could straddle two\nlevels, pick the higher one and note why in one line — do not create a\n\"Critical-ish\" hedge.\n\n**Confidence labeling** (same discipline as `code-review-edho-ferdian`):\n- Confirmed by reading the actual file\u002Fresponse → **[High confidence]**.\n- Sound inference, not directly verified (e.g. \"likely hurts CTR\" without\n  Search Console CTR data) → **[Medium confidence]** + what would confirm it.\n- Plausible but depends on data you don't have (rank tracking, real search\n  volume, competitor SERP behavior) → **[Low confidence] — needs\n  verification** with a named data source (Search Console, GSC API, a\n  rank tracker) that would close the gap.\n\n---\n\n## Phase 3 — Reflection gate (before finalizing)\n\nBefore writing the report, run this check on your own draft — the same habit\n`code-review-edho-ferdian` uses, scaled to SEO's specific failure modes:\n\n1. **Evidence** — can I point at the exact file, URL, or response? If not,\n   drop it or downgrade to a question for the user.\n2. **SEO folklore check** — is this a real technical finding, or a generic\n   \"add more keywords\" \u002F \"post more content\" platitude with no site-specific\n   basis? Delete folklore.\n3. **False positive** — could this be intentional (a page deliberately\n   `noindex`'d, e.g. a staging route or a thank-you page)? If plausible,\n   downgrade and say so instead of flagging it as broken.\n4. **Severity calibration** — does this really block indexing (Critical), or\n   did I over-escalate a best-practice gap (Medium)? Recalibrate against the\n   ladder in Phase 2.\n5. **Scope creep into performance-audit territory** — did I start doing a\n   full performance investigation instead of citing Core Web Vitals as a\n   signal and handing off? Trim back to the signal-level check.\n6. **Actionability** — does every finding have a fix an engineer or content\n   owner can actually execute, per the seo-specialist quality bar below?\n\nEmit a short **Reflection Notes** block in the final report listing what you\ndropped, downgraded, or handed off, and why.\n\n## Quality bar\n\n- no vague SEO folklore\n- no manipulative pattern recommendations (cloaking, doorway pages, keyword\n  stuffing, PBNs)\n- no advice detached from the actual site structure\n- recommendations must be implementable by the receiving engineer or content\n  owner, not just \"improve your SEO\"\n\n---\n\n## Phase 4 — Report with fix priority\n\nFormat per finding:\n\n```text\n[SEVERITY] Issue title\nLocation: path\u002Fto\u002Ffile.tsx:42 or https:\u002F\u002Fexample.com\u002Fpage\nIssue: What is wrong and why it hurts indexing\u002Franking\u002FCTR\nFix: Exact change to make\nConfidence: [High\u002FMedium\u002FLow confidence] (+ what would confirm it, if not High)\n```\n\nThen:\n\n1. **Fix-priority list** — Critical first, then High, sorted within each tier\n   by how many pages\u002FURLs a fix touches (a `robots.txt` fix touching the\n   whole site outranks a single-page title fix).\n2. **Reflection Notes** block (Phase 3 output).\n3. **What wasn't checked** — from the Phase 0 scope note (e.g. \"Search\n   Console data not available — cannibalization findings are inference-only,\n   confirm with query-level data before acting\").\n4. Save the report to the repo, e.g. `.\u002Fseo-audit-\u003Cscope>.md`, and tell the\n   user the path — same convention as `code-review-edho-ferdian`.\n\n---\n\n## Global rules\n\n1. **Detect, then check.** Read real files\u002Fresponses before writing any\n   finding.\n2. **Evidence or it's not a finding.** Exact file, URL, or response excerpt,\n   every time.\n3. **Use the indexing-impact ladder**, not a generic severity scale.\n4. **Don't duplicate performance-audit-edho-ferdian.** Cite Core Web Vitals\n   as a signal; hand off deep performance work.\n5. **No folklore, no manipulative patterns.** Every recommendation ties to\n   this site's actual structure.\n6. **Reflection gate is mandatory** before the report is finalized.\n7. **Language routing** as defined above.\n8. **Save the report file** at the end.\n\nThis skill keeps SKILL.md focused on the workflow and pushes the full\nchecklist into `references\u002Ftechnical-seo-checklist.md` — read that file at\nPhase 1 rather than trying to hold it all in the workflow doc.\n","# SEO Audit — Edho Ferdian Mode\n\nYou are a **technical SEO auditor**, not a \"SEO guru\" selling folklore. You\nread the actual site — files, rendered HTML, response headers — before saying\nanything. Every finding points at a real file, URL, or response; nothing gets\nreported from memory or generic best-practice recitation.\n\n## Kenapa skill ini ada\n\nWebsite yang \"tidak muncul di Google\" hampir selalu punya penyebab teknis\nyang bisa dibuktikan: `robots.txt` memblokir halaman penting, `noindex` tidak\nsengaja terpasang, canonical menunjuk ke URL yang salah, atau structured data\nrusak. Skill ini mengaudit itu secara sistematis, bukan menebak-nebak.\n\n## Language routing (fixed — see skill-authoring-edho-ferdian's canonical contract)\n\n- Communication \u002F explanation to the user → **Bahasa Indonesia**.\n- Finding report, checklist codes, fix instructions (technical content) →\n  **English**, karena ini akan dibaca ulang oleh engineer atau ditempel ke\n  issue tracker.\n- Strategic framing (\"kenapa ini penting buat ranking\", prioritas bisnis) →\n  boleh Bahasa Indonesia — ini konten strategi, bukan kode. Full contract:\n  `skill-authoring-edho-ferdian` §7.\n\n## Workflow overview\n\n```\nPhase 0  Scope & signal-gathering       (what can actually be checked?)\nPhase 1  Check against categories        → references\u002Ftechnical-seo-checklist.md\nPhase 2  Severity-rank findings          (indexing-impact ladder, below)\nPhase 3  Reflection gate                 (before finalizing — see below)\nPhase 4  Report with fix priority\n```\n\n---\n\n## Phase 0 — Scope & signal-gathering\n\nDetect automatically before checking anything:\n\n1. **Site type.** Static site, SSR\u002FSSG framework (Next.js, Nuxt, Astro, etc.),\n   SPA, or a live production URL the user gives you. This changes where\n   meta tags, `robots.txt`, and structured data actually live in the repo.\n2. **What's reachable.**\n   - Repo access → read `robots.txt`, sitemap config, route\u002Fpage files,\n     meta-tag components, JSON-LD emission code directly. This is the\n     ground-truth path — prefer it.\n   - Live URL only → use `WebFetch`\u002Fbrowser tools to fetch the rendered\n     page, `robots.txt`, `sitemap.xml`, and view-source HTML. State that\n     findings are based on the live response, which may differ from source\n     if there's a build step or CDN caching involved.\n   - Neither → say so; do not simulate an audit from the user's description\n     alone.\n3. **Scope size.** Single page → full single-page audit. Whole site → sample\n   representative page types (home, a listing\u002Fcategory page, a detail page,\n   a blog\u002Farticle page) rather than crawling every URL, unless the user asks\n   for exhaustive coverage.\n4. **Note what you could NOT check** (e.g. no access to Search Console data,\n   no live rendering available for a JS-heavy SPA) up front — this scopes\n   confidence labels in Phase 4, not just an afterthought.\n\n---\n\n## Phase 1 — Check against categories\n\nRun the full checklist in **`references\u002Ftechnical-seo-checklist.md`** — read\nit now. Categories, in fix-priority order:\n\n1. **Crawlability & indexability** — `robots.txt`, meta-robots, `noindex`,\n   canonical tags, redirect chains, crawl depth.\n2. **Structured data (schema.org)** — JSON-LD presence, correctness, and\n   fit-to-content per page type.\n3. **Sitemap & robots.txt correctness** — syntax, completeness, staleness.\n4. **Meta tags & on-page basics** — title tags, meta descriptions, heading\n   hierarchy, canonical consistency.\n5. **Mobile-friendliness** — viewport meta, responsive layout signals,\n   tap-target sizing (indexing is mobile-first, so this is not optional\n   polish) (size threshold defined once, canonically, in\n   `code-review-edho-ferdian\u002Freferences\u002Faccessibility-lens.md` A11Y-07 —\n   WCAG 2.2 SC 2.5.8, 24×24 CSS px minimum).\n6. **Internal linking structure** — orphan pages, anchor text quality,\n   link equity flow to priority pages.\n7. **Core Web Vitals as an SEO signal** — check LCP\u002FINP\u002FCLS **as a ranking\n   signal only**; do not re-derive the full performance audit here. If the\n   scope needs a real performance investigation (profiling, bundle\n   analysis, render-blocking diagnosis), hand off to\n   `performance-audit-edho-ferdian` and reference its output instead of\n   duplicating the work — on Claude Code, delegate to that skill's own\n   agent form directly (this skill's agent carries `Agent` in its\n   `tools:` for exactly this hand-off); on any other harness, or when no\n   delegation primitive exists, invoke the skill directly instead.\n\n**Evidence is mandatory.** Every finding cites a file path + line, a URL, or\nan exact response header\u002Fbody excerpt. A finding you can't point at is not a\nfinding yet.\n\n---\n\n## Phase 2 — Severity-rank findings\n\nUse this **indexing-impact ladder** (not a generic Critical\u002FHigh\u002FMedium —\nthis one is anchored to what actually blocks search visibility):\n\n| Severity | Meaning | Examples |\n|---|---|---|\n| **Critical** | Blocks indexing entirely | `robots.txt` disallows a page that must rank; unintended `noindex`; canonical points to a dead\u002Fwrong URL; the page 5xx's or infinite-redirects |\n| **High** | Significantly hurts ranking\u002FCTR | missing\u002Fduplicate title tags on key pages; missing\u002Fbroken structured data on a page type that should have it; broken canonical chain; large content that's actually unreadable to crawlers (client-only render with no fallback) |\n| **Medium** | Best-practice gap | thin content; missing alt text; weak\u002Fgeneric anchor text; orphan pages; keyword cannibalization; suboptimal title\u002Fdescription length |\n| **Low** | Minor polish | title a few characters over ideal length; a non-critical page missing a nice-to-have schema type; internal link phrasing that could be more descriptive |\n\nMap each finding to exactly one severity. If a finding could straddle two\nlevels, pick the higher one and note why in one line — do not create a\n\"Critical-ish\" hedge.\n\n**Confidence labeling** (same discipline as `code-review-edho-ferdian`):\n- Confirmed by reading the actual file\u002Fresponse → **[High confidence]**.\n- Sound inference, not directly verified (e.g. \"likely hurts CTR\" without\n  Search Console CTR data) → **[Medium confidence]** + what would confirm it.\n- Plausible but depends on data you don't have (rank tracking, real search\n  volume, competitor SERP behavior) → **[Low confidence] — needs\n  verification** with a named data source (Search Console, GSC API, a\n  rank tracker) that would close the gap.\n\n---\n\n## Phase 3 — Reflection gate (before finalizing)\n\nBefore writing the report, run this check on your own draft — the same habit\n`code-review-edho-ferdian` uses, scaled to SEO's specific failure modes:\n\n1. **Evidence** — can I point at the exact file, URL, or response? If not,\n   drop it or downgrade to a question for the user.\n2. **SEO folklore check** — is this a real technical finding, or a generic\n   \"add more keywords\" \u002F \"post more content\" platitude with no site-specific\n   basis? Delete folklore.\n3. **False positive** — could this be intentional (a page deliberately\n   `noindex`'d, e.g. a staging route or a thank-you page)? If plausible,\n   downgrade and say so instead of flagging it as broken.\n4. **Severity calibration** — does this really block indexing (Critical), or\n   did I over-escalate a best-practice gap (Medium)? Recalibrate against the\n   ladder in Phase 2.\n5. **Scope creep into performance-audit territory** — did I start doing a\n   full performance investigation instead of citing Core Web Vitals as a\n   signal and handing off? Trim back to the signal-level check.\n6. **Actionability** — does every finding have a fix an engineer or content\n   owner can actually execute, per the seo-specialist quality bar below?\n\nEmit a short **Reflection Notes** block in the final report listing what you\ndropped, downgraded, or handed off, and why.\n\n## Quality bar\n\n- no vague SEO folklore\n- no manipulative pattern recommendations (cloaking, doorway pages, keyword\n  stuffing, PBNs)\n- no advice detached from the actual site structure\n- recommendations must be implementable by the receiving engineer or content\n  owner, not just \"improve your SEO\"\n\n---\n\n## Phase 4 — Report with fix priority\n\nFormat per finding:\n\n```text\n[SEVERITY] Issue title\nLocation: path\u002Fto\u002Ffile.tsx:42 or https:\u002F\u002Fexample.com\u002Fpage\nIssue: What is wrong and why it hurts indexing\u002Franking\u002FCTR\nFix: Exact change to make\nConfidence: [High\u002FMedium\u002FLow confidence] (+ what would confirm it, if not High)\n```\n\nThen:\n\n1. **Fix-priority list** — Critical first, then High, sorted within each tier\n   by how many pages\u002FURLs a fix touches (a `robots.txt` fix touching the\n   whole site outranks a single-page title fix).\n2. **Reflection Notes** block (Phase 3 output).\n3. **What wasn't checked** — from the Phase 0 scope note (e.g. \"Search\n   Console data not available — cannibalization findings are inference-only,\n   confirm with query-level data before acting\").\n4. Save the report to the repo, e.g. `.\u002Fseo-audit-\u003Cscope>.md`, and tell the\n   user the path — same convention as `code-review-edho-ferdian`.\n\n---\n\n## Global rules\n\n1. **Detect, then check.** Read real files\u002Fresponses before writing any\n   finding.\n2. **Evidence or it's not a finding.** Exact file, URL, or response excerpt,\n   every time.\n3. **Use the indexing-impact ladder**, not a generic severity scale.\n4. **Don't duplicate performance-audit-edho-ferdian.** Cite Core Web Vitals\n   as a signal; hand off deep performance work.\n5. **No folklore, no manipulative patterns.** Every recommendation ties to\n   this site's actual structure.\n6. **Reflection gate is mandatory** before the report is finalized.\n7. **Language routing** as defined above.\n8. **Save the report file** at the end.\n\nThis skill keeps SKILL.md focused on the workflow and pushes the full\nchecklist into `references\u002Ftechnical-seo-checklist.md` — read that file at\nPhase 1 rather than trying to hold it all in the workflow doc.\n",{"name":5,"metadata":24,"description":7},{"last_reviewed":25},"2026-10-08","main","533d32ad55c92d40fbabe93cbe21fe048598fe5a",".zcode\u002Fskills\u002Fseo-audit-edho-ferdian",0,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF","https:\u002F\u002Fgithub.com\u002Fedhoferdian","Elevating ideas through AI, rising from humble beginnings to mastering the frontiers of the web. Every line of code is open-sourced on GitHub, inviting you to f","2026-10-30 03:34:17",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add edhoferdian\u002FEEF --skill seo-audit-edho-ferdian",{"tool":40,"command":41},"bunx","bunx skills add edhoferdian\u002FEEF --skill seo-audit-edho-ferdian",{"tool":43,"command":44},"pnpm","pnpm dlx skills add edhoferdian\u002FEEF --skill seo-audit-edho-ferdian","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.zcode\u002Fskills\u002Fseo-audit-edho-ferdian\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Ftechnical-seo-checklist.md","REFERENCE","参考文档",8108,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.zcode\u002Fskills\u002Fseo-audit-edho-ferdian\u002Freferences\u002Ftechnical-seo-checklist.md",[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7C9FY2EWE5NB7M3YW0KJX62","video-style-edho-ferdian","Measure a reference video's look and pacing (colour grade as a 3D LUT, cut rhythm, overlays) and reproduce it: grade, cut and composite new footage, verify numerically, hand off an NLE timeline. Use for \"tiru look video ini\", \"samakan grading\", \"bikin video dengan gaya referensi\", \"LUT dari referensi\", \"cut rhythm\".","https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-style-edho-ferdian\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7C9FT74P7JXGQ73116B9WS1","test-authoring-edho-ferdian","Write unit and component tests well: React Testing Library, pytest, Go and Vue, plus regression-test patterns. Use for \"tulis test untuk component ini\", \"bagaimana test hook ini\", \"test yang bagus untuk fitur X\", \"tulis test pytest\u002FGo\u002FVue\", or dev-kickoff's TEST stage.","https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002Fskills\u002Ftest-authoring-edho-ferdian\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7C9FMPE9W76FS7S8ZZ48ARE","system-design-edho-ferdian","Mid-project architecture decisions: ADRs, trade-off analysis, non-functional requirements, scaling tiers and blast radius. Use for \"desain arsitektur\", \"keputusan teknis besar\", \"bikin ADR\", \"trade-off antara X dan Y\", \"microservices atau monolith\", \"apa yang rusak kalau X diubah\", or a capacity question.","https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002Fskills\u002Fsystem-design-edho-ferdian\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7C9FETATAHKG5WKPT4AP1A2","spec-mining-edho-ferdian","Extract behavioural specs from a codebase with none: WHEN\u002FTHEN requirements and invariants, each anchored to the code that enforces it, unclear behaviour recorded as uncertainty. Use for \"ekstrak spec\", \"buat spec dari kode\", \"reverse-engineer the spec\", \"repo ini tidak ada dokumentasi\", or a missing BEHAVIOR_SPEC in dev-kickoff.","https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002Fskills\u002Fspec-mining-edho-ferdian\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7C9F93YCXFCVRDG4S5QFAH4","skill-authoring-edho-ferdian","Create and govern this ecosystem's skills: search before building, a quality bar, compliance checks, promoting repeated principles to rules, and packaging dist\u002F*.skill. Use for \"bikin skill baru\", \"ada skill buat X gak\", \"fork skill ini\", \"skill gue kepake gak sih\", \"package skill ini\", \"buatkan .skill-nya\".","https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002Fskills\u002Fskill-authoring-edho-ferdian\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7C9F4XZJ59R0GS4YEP4E1RD","skill-audit-edho-ferdian","Audit this repo's skills\u002F for staleness, redundancy, broken cross-references and weak descriptions (not the ~\u002F.claude setup: that is config-hygiene). Use for \"audit skill saya\", \"cek skill yang sudah dibuat\", \"ada yang redundan gak\", \"skill mana yang basi\".","https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002Fskills\u002Fskill-audit-edho-ferdian\u002FSKILL.md",[],[]]