[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A6Q90F1WHVM72749964AVC":3,"skill-same:01M7A6Q90F1WHVM72749964AVC":67},{"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":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M7A6Q90F1WHVM72749964AVC","mdpr-skill",null,"Review MDPR Markdown presentation workflows with semantic hints, visual checks, and deterministic renderer boundaries.","MHassan0000\u002FSkills","MHassan0000","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F224296448?v=4","01M7A14DTC1EZCRN04582533RD","Muhammad Hassan Yousaf","01M7A14DV10KTW8NHQTJPD08X0",1,"MIT","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fmdpr-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mdpr-skill\ndescription: \"Review MDPR Markdown presentation workflows with semantic hints, visual checks, and deterministic renderer boundaries.\"\ncategory: productivity\nrisk: safe\nsource: community\nsource_repo: ch040602\u002Fmdpr-skill\nsource_type: community\ndate_added: \"2026-07-01\"\nauthor: ch040602\ntags: [mdpr, presentations, markdown, powerpoint, codex, visual-review, agent-hints]\ntools: [claude, cursor, gemini, codex, antigravity]\nlicense: \"MIT\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002Fch040602\u002Fmdpr-skill\u002Fblob\u002Fmain\u002FLICENSE\"\n---\n\n# mdpr-skill\n\n## Overview\n\nUse this skill as the optional agent companion for\n[MDPR](https:\u002F\u002Fgithub.com\u002Fch040602\u002FMdPr), a deterministic\nMarkdown-to-presentation runtime. MDPR owns parsing, layout, theming,\nvalidation, and final PPTX\u002FHTML\u002FPDF rendering. This skill helps an agent review\nMDPR workflows, propose weak semantic hints, and explain visual findings without\ntaking control of slide geometry.\n\nThe upstream skill source is\n[`ch040602\u002Fmdpr-skill`](https:\u002F\u002Fgithub.com\u002Fch040602\u002Fmdpr-skill), which includes\nschemas, review commands, compatibility artifacts, visual evidence examples, and\nMDPR boundary documentation.\n\n## When to Use This Skill\n\n- Use when the user asks about MDPR, `mdpresent`, Markdown-to-PPTX, or\n  Markdown presentation review.\n- Use when generated MDPR artifacts need semantic, narrative, accessibility, or\n  visual review notes.\n- Use when the user wants Codex-style presentation workflow hints while keeping\n  MDPR as the deterministic renderer.\n- Use when comparing MDPR output against image-only deck generators such as a\n  codex-ppt style workflow.\n- Use when a reusable theme or style-pack proposal should be expressed as an\n  approval-bound MDPR candidate instead of direct final slide edits.\n\n## Core Boundary\n\n- Let MDPR own parsing, slide splitting, recipes, layout, coordinates,\n  geometry, typography, colors, z-order, arrows, effects, exact icon assets,\n  renderer object IDs, and final PPTX objects.\n- Keep agent output semantic, evidence-based, and schema-valid.\n- Express fixes as Markdown cleanup, MDPR rulebook changes, config changes,\n  deterministic policy changes, or approval-bound proposals.\n- Preserve the ability to build the same deck with all agent hints disabled.\n- Do not mutate source Markdown unless the user explicitly asks for a cleaned\n  source draft.\n\n## How It Works\n\n### Step 1: Identify the MDPR Surface\n\nClassify the user's request before producing advice:\n\n- `semantic hints`: compact intent, grouping, importance, and icon-keyword\n  suggestions.\n- `review report`: visual or narrative concerns grounded in rendered evidence,\n  manifests, or validation reports.\n- `layout intent`: high-level layout goals from a summarized template catalog,\n  never concrete placeholder coordinates.\n- `theme candidate`: reusable token and style-pack proposal for later MDPR\n  approval\u002Fimport gates.\n- `codex-ppt compatibility`: feature mapping and comparison notes only; do not\n  turn MDPR into a full-slide image renderer.\n\n### Step 2: Ground Every Finding\n\nReference available evidence such as:\n\n- source Markdown path or heading text\n- MDPR manifest summaries\n- rendered preview image paths\n- validation report IDs\n- source notes or citation metadata\n- schema names such as `agent-hint.json`, `review-report.json`, or\n  `mdpr-theme-candidate-v1`\n\nIf evidence is missing, say what artifact is needed instead of inventing a\npass\u002Ffail result.\n\n### Step 3: Keep Hints Weak\n\nAllowed hints:\n\n- slide or section intent\n- content grouping\n- relative importance\n- icon-search keywords\n- accessibility or citation review notes\n- generated-image candidate briefs when an icon would be too small or too\n  semantically ambiguous\n\nDisallowed hints:\n\n- final coordinates, sizes, z-order, geometry, or object IDs\n- exact colors, typography, arrows, effects, or icon asset choices\n- final layout IDs or placeholder IDs\n- pass\u002Ffail validation decisions not backed by MDPR validation\n\n### Step 4: Route Fixes to MDPR-Owned Changes\n\nWhen repeated issues appear, recommend a deterministic follow-up surface:\n\n- Markdown cleanup\n- MDPR rulebook change\n- MDPR config\u002Fprofile change\n- MDPR theme-pack registration\n- MDPR validation improvement\n- approval-bound deck-local override or style-pack candidate\n\n## Useful Local Commands\n\nRun these only when the upstream `mdpr-skill` CLI is available in the current\nworkspace and the referenced input files exist.\n\n```bash\nnode bin\u002Fmdpr-skill.js hint --source-sha256 \u003C64hex> --out .mdpresent\u002Fproposals\u002Fagent-hint.json\nnode bin\u002Fmdpr-skill.js review --manifest dist\u002Fmdpresent-manifest.json --out .mdpresent\u002Freview\u002Freview-report.json\nnode bin\u002Fmdpr-skill.js narrative --markdown deck.md --manifest dist\u002Fmdpresent-manifest.json --out .mdpresent\u002Freview\u002Fnarrative-review.json\nnode bin\u002Fmdpr-skill.js layout-intent --layout-catalog template-layout-catalog.json --out .mdpresent\u002Freview\u002Flayout-intent.json\nnode bin\u002Fmdpr-skill.js accessibility --markdown deck.md --audience \"executive review\" --out .mdpresent\u002Freview\u002Faccessibility-review.json\n```\n\n## Examples\n\n### Review a Rendered MDPR Deck\n\n1. Read the source Markdown, manifest summary, rendered image list, and any\n   validation report.\n2. Separate source-content problems from renderer\u002Frulebook problems.\n3. Report only evidence-backed visual concerns.\n4. Recommend deterministic MDPR fixes when the same issue repeats.\n\n```markdown\nFinding: Slide 4 has weak visual hierarchy between the metric and explanation.\nEvidence: rendered\u002Fslide-04.png, manifest slide id `s4`, heading \"Revenue Mix\".\nMDPR-owned fix: adjust the metric-card recipe spacing rule or choose a\ndeterministic layout profile with stronger numeric emphasis.\n```\n\n### Propose a Theme Candidate\n\n1. Treat the source design as a visual system, not content to copy.\n2. Extract reusable tokens, semantic layout blueprints, decoration grammar, and\n   best-fit scenarios.\n3. Emit an approval-bound `mdpr-theme-candidate-v1`.\n4. Keep `mdprOwnsFinalLayout`, `mdprOwnsFinalThemeBinding`, and\n   `noRawUseInAgentHints` true.\n\n```json\n{\n  \"schema\": \"mdpr-theme-candidate-v1\",\n  \"source\": \"rendered reference set approved by user\",\n  \"useCases\": [\"executive review\", \"research update\"],\n  \"constraints\": {\n    \"mdprOwnsFinalLayout\": true,\n    \"mdprOwnsFinalThemeBinding\": true,\n    \"noRawUseInAgentHints\": true\n  }\n}\n```\n\n### Compare with codex-ppt Style Workflows\n\nUse codex-ppt only as a capability reference or image-only baseline. Preserve\nthe output-model distinction: codex-ppt style workflows may produce full-slide\nimages, while MDPR defaults to editable PPTX\u002FHTML\u002FPDF with deterministic\nvalidation.\n\n```markdown\nComparison note: codex-ppt style output may optimize for a single rasterized\nslide image. MDPR should instead preserve editable slide objects and route\nvisual improvements through recipes, themes, and validation policies.\n```\n\n## Best Practices\n\n- Do: Prefer concise semantic hints over restating the source.\n- Do: Keep review notes actionable for MDPR maintainers.\n- Do: Call out missing evidence before making quality claims.\n- Do: Treat LLM judgment as triage only; MDPR validation remains the release\n  gate.\n- Avoid: Turning generated asset prompts into final asset selections.\n- Avoid: Recommending raw colors, coordinates, or renderer object IDs from\n  agent judgment alone.\n\n## Limitations\n\n- This skill does not replace MDPR runtime validation.\n- This skill does not generate final slide coordinates or final PPTX objects.\n- This skill does not make MDPR depend on an LLM.\n- This skill should not be used to copy private deck designs or proprietary\n  slide content.\n\n## Common Pitfalls\n\n- **Problem:** Treating mdpr-skill output as final slide layout.\n  **Solution:** Keep hints semantic and let MDPR choose final layout, geometry,\n  and renderer objects.\n\n- **Problem:** Reporting visual issues without evidence.\n  **Solution:** Link each finding to source Markdown, a manifest entry, rendered\n  previews, validation reports, or another concrete artifact.\n\n- **Problem:** Copying codex-ppt image-only behavior into MDPR.\n  **Solution:** Use image-only generators as comparison baselines while\n  preserving MDPR's editable PPTX\u002FHTML\u002FPDF output model.\n\n## Security & Safety Notes\n\n- Review only files the user has provided or authorized.\n- Do not fetch private references, credentials, or paid assets without explicit\n  permission.\n- Do not include secrets, API keys, or private source content in generated\n  review reports or theme candidates.\n- Treat all CLI commands as local workspace commands; confirm input paths exist\n  before running them.\n\n## Related Skills\n\n- `@frontend-slides` - Use for browser-native HTML presentation generation.\n- `@2slides-ppt-generator` - Use for hosted API-based presentation generation.\n- `@office-productivity` - Use for broader document, spreadsheet, and slide\n  workflow coordination.\n","# mdpr-skill\n\n## Overview\n\nUse this skill as the optional agent companion for\n[MDPR](https:\u002F\u002Fgithub.com\u002Fch040602\u002FMdPr), a deterministic\nMarkdown-to-presentation runtime. MDPR owns parsing, layout, theming,\nvalidation, and final PPTX\u002FHTML\u002FPDF rendering. This skill helps an agent review\nMDPR workflows, propose weak semantic hints, and explain visual findings without\ntaking control of slide geometry.\n\nThe upstream skill source is\n[`ch040602\u002Fmdpr-skill`](https:\u002F\u002Fgithub.com\u002Fch040602\u002Fmdpr-skill), which includes\nschemas, review commands, compatibility artifacts, visual evidence examples, and\nMDPR boundary documentation.\n\n## When to Use This Skill\n\n- Use when the user asks about MDPR, `mdpresent`, Markdown-to-PPTX, or\n  Markdown presentation review.\n- Use when generated MDPR artifacts need semantic, narrative, accessibility, or\n  visual review notes.\n- Use when the user wants Codex-style presentation workflow hints while keeping\n  MDPR as the deterministic renderer.\n- Use when comparing MDPR output against image-only deck generators such as a\n  codex-ppt style workflow.\n- Use when a reusable theme or style-pack proposal should be expressed as an\n  approval-bound MDPR candidate instead of direct final slide edits.\n\n## Core Boundary\n\n- Let MDPR own parsing, slide splitting, recipes, layout, coordinates,\n  geometry, typography, colors, z-order, arrows, effects, exact icon assets,\n  renderer object IDs, and final PPTX objects.\n- Keep agent output semantic, evidence-based, and schema-valid.\n- Express fixes as Markdown cleanup, MDPR rulebook changes, config changes,\n  deterministic policy changes, or approval-bound proposals.\n- Preserve the ability to build the same deck with all agent hints disabled.\n- Do not mutate source Markdown unless the user explicitly asks for a cleaned\n  source draft.\n\n## How It Works\n\n### Step 1: Identify the MDPR Surface\n\nClassify the user's request before producing advice:\n\n- `semantic hints`: compact intent, grouping, importance, and icon-keyword\n  suggestions.\n- `review report`: visual or narrative concerns grounded in rendered evidence,\n  manifests, or validation reports.\n- `layout intent`: high-level layout goals from a summarized template catalog,\n  never concrete placeholder coordinates.\n- `theme candidate`: reusable token and style-pack proposal for later MDPR\n  approval\u002Fimport gates.\n- `codex-ppt compatibility`: feature mapping and comparison notes only; do not\n  turn MDPR into a full-slide image renderer.\n\n### Step 2: Ground Every Finding\n\nReference available evidence such as:\n\n- source Markdown path or heading text\n- MDPR manifest summaries\n- rendered preview image paths\n- validation report IDs\n- source notes or citation metadata\n- schema names such as `agent-hint.json`, `review-report.json`, or\n  `mdpr-theme-candidate-v1`\n\nIf evidence is missing, say what artifact is needed instead of inventing a\npass\u002Ffail result.\n\n### Step 3: Keep Hints Weak\n\nAllowed hints:\n\n- slide or section intent\n- content grouping\n- relative importance\n- icon-search keywords\n- accessibility or citation review notes\n- generated-image candidate briefs when an icon would be too small or too\n  semantically ambiguous\n\nDisallowed hints:\n\n- final coordinates, sizes, z-order, geometry, or object IDs\n- exact colors, typography, arrows, effects, or icon asset choices\n- final layout IDs or placeholder IDs\n- pass\u002Ffail validation decisions not backed by MDPR validation\n\n### Step 4: Route Fixes to MDPR-Owned Changes\n\nWhen repeated issues appear, recommend a deterministic follow-up surface:\n\n- Markdown cleanup\n- MDPR rulebook change\n- MDPR config\u002Fprofile change\n- MDPR theme-pack registration\n- MDPR validation improvement\n- approval-bound deck-local override or style-pack candidate\n\n## Useful Local Commands\n\nRun these only when the upstream `mdpr-skill` CLI is available in the current\nworkspace and the referenced input files exist.\n\n```bash\nnode bin\u002Fmdpr-skill.js hint --source-sha256 \u003C64hex> --out .mdpresent\u002Fproposals\u002Fagent-hint.json\nnode bin\u002Fmdpr-skill.js review --manifest dist\u002Fmdpresent-manifest.json --out .mdpresent\u002Freview\u002Freview-report.json\nnode bin\u002Fmdpr-skill.js narrative --markdown deck.md --manifest dist\u002Fmdpresent-manifest.json --out .mdpresent\u002Freview\u002Fnarrative-review.json\nnode bin\u002Fmdpr-skill.js layout-intent --layout-catalog template-layout-catalog.json --out .mdpresent\u002Freview\u002Flayout-intent.json\nnode bin\u002Fmdpr-skill.js accessibility --markdown deck.md --audience \"executive review\" --out .mdpresent\u002Freview\u002Faccessibility-review.json\n```\n\n## Examples\n\n### Review a Rendered MDPR Deck\n\n1. Read the source Markdown, manifest summary, rendered image list, and any\n   validation report.\n2. Separate source-content problems from renderer\u002Frulebook problems.\n3. Report only evidence-backed visual concerns.\n4. Recommend deterministic MDPR fixes when the same issue repeats.\n\n```markdown\nFinding: Slide 4 has weak visual hierarchy between the metric and explanation.\nEvidence: rendered\u002Fslide-04.png, manifest slide id `s4`, heading \"Revenue Mix\".\nMDPR-owned fix: adjust the metric-card recipe spacing rule or choose a\ndeterministic layout profile with stronger numeric emphasis.\n```\n\n### Propose a Theme Candidate\n\n1. Treat the source design as a visual system, not content to copy.\n2. Extract reusable tokens, semantic layout blueprints, decoration grammar, and\n   best-fit scenarios.\n3. Emit an approval-bound `mdpr-theme-candidate-v1`.\n4. Keep `mdprOwnsFinalLayout`, `mdprOwnsFinalThemeBinding`, and\n   `noRawUseInAgentHints` true.\n\n```json\n{\n  \"schema\": \"mdpr-theme-candidate-v1\",\n  \"source\": \"rendered reference set approved by user\",\n  \"useCases\": [\"executive review\", \"research update\"],\n  \"constraints\": {\n    \"mdprOwnsFinalLayout\": true,\n    \"mdprOwnsFinalThemeBinding\": true,\n    \"noRawUseInAgentHints\": true\n  }\n}\n```\n\n### Compare with codex-ppt Style Workflows\n\nUse codex-ppt only as a capability reference or image-only baseline. Preserve\nthe output-model distinction: codex-ppt style workflows may produce full-slide\nimages, while MDPR defaults to editable PPTX\u002FHTML\u002FPDF with deterministic\nvalidation.\n\n```markdown\nComparison note: codex-ppt style output may optimize for a single rasterized\nslide image. MDPR should instead preserve editable slide objects and route\nvisual improvements through recipes, themes, and validation policies.\n```\n\n## Best Practices\n\n- Do: Prefer concise semantic hints over restating the source.\n- Do: Keep review notes actionable for MDPR maintainers.\n- Do: Call out missing evidence before making quality claims.\n- Do: Treat LLM judgment as triage only; MDPR validation remains the release\n  gate.\n- Avoid: Turning generated asset prompts into final asset selections.\n- Avoid: Recommending raw colors, coordinates, or renderer object IDs from\n  agent judgment alone.\n\n## Limitations\n\n- This skill does not replace MDPR runtime validation.\n- This skill does not generate final slide coordinates or final PPTX objects.\n- This skill does not make MDPR depend on an LLM.\n- This skill should not be used to copy private deck designs or proprietary\n  slide content.\n\n## Common Pitfalls\n\n- **Problem:** Treating mdpr-skill output as final slide layout.\n  **Solution:** Keep hints semantic and let MDPR choose final layout, geometry,\n  and renderer objects.\n\n- **Problem:** Reporting visual issues without evidence.\n  **Solution:** Link each finding to source Markdown, a manifest entry, rendered\n  previews, validation reports, or another concrete artifact.\n\n- **Problem:** Copying codex-ppt image-only behavior into MDPR.\n  **Solution:** Use image-only generators as comparison baselines while\n  preserving MDPR's editable PPTX\u002FHTML\u002FPDF output model.\n\n## Security & Safety Notes\n\n- Review only files the user has provided or authorized.\n- Do not fetch private references, credentials, or paid assets without explicit\n  permission.\n- Do not include secrets, API keys, or private source content in generated\n  review reports or theme candidates.\n- Treat all CLI commands as local workspace commands; confirm input paths exist\n  before running them.\n\n## Related Skills\n\n- `@frontend-slides` - Use for browser-native HTML presentation generation.\n- `@2slides-ppt-generator` - Use for hosted API-based presentation generation.\n- `@office-productivity` - Use for broader document, spreadsheet, and slide\n  workflow coordination.\n",{"name":5,"risk":24,"tags":25,"tools":33,"author":38,"source":39,"license":15,"category":40,"date_added":41,"description":7,"source_repo":42,"source_type":39,"license_source":43},"safe",[26,27,28,29,30,31,32],"mdpr","presentations","markdown","powerpoint","codex","visual-review","agent-hints",[34,35,36,30,37],"claude","cursor","gemini","antigravity","ch040602","community","productivity","2026-07-01","ch040602\u002Fmdpr-skill","https:\u002F\u002Fgithub.com\u002Fch040602\u002Fmdpr-skill\u002Fblob\u002Fmain\u002FLICENSE","main","a4404a75dc81d6b7e58c5906b6aaffbcb5e84747","Claude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fmdpr-skill",0,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills","https:\u002F\u002Fgithub.com\u002FMHassan0000","https:\u002F\u002Fhassanyousaf.vercel.app","Full Stack Developer building web apps, SaaS, AI systems, and automations. Passionate about clean code, UI\u002FUX, backend systems, and turning ideas into products.","2026-08-07 20:42:05",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add MHassan0000\u002FSkills --skill mdpr-skill",{"tool":59,"command":60},"bunx","bunx skills add MHassan0000\u002FSkills --skill mdpr-skill",{"tool":62,"command":63},"pnpm","pnpm dlx skills add MHassan0000\u002FSkills --skill mdpr-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fmdpr-skill\u002FSKILL.md",true,[],[68,75,82,89,98,106],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7AGBX58S04DX8DKKME8N311","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7AGBREE890608Z7YDMAKH27","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells and produce more human-like writing.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fstop-slop\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7AGAS972A2AN7Q5EW8HEAXK","ogilvy-copywriting","Apply David Ogilvy's advertising principles when writing or reviewing copy, headlines, product descriptions, landing pages, ads, emails, or any persuasive text. Use when the goal is copy that sells, not copy that wins awards. Covers positioning, headlines, promises, brand voice, long-form copy, and visual logic. Source: How to Create Advertising That Sells (1972) + Ogilvy on Advertising.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fogilvy\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7AGAF12803G5JPVMK79AYJB","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7AG88WWVWCGJY9WA9CH7EY4","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7AG7ZTNV7XQCWDQ9674FBYB","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[]]