[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0H9CP45DB8KFE2RPC0MWC":3,"skill-same:01M7F0H9CP45DB8KFE2RPC0MWC":87},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7F0H9CP45DB8KFE2RPC0MWC","linkedin-strategy",null,"Use when someone needs a LinkedIn plan rather than a post — content pillars, positioning for a career change or consulting or thought leadership, a sustainable posting cadence, or a newsletter decision. Triggers on \"what should I post about\", \"how often should I post\", \"LinkedIn content strategy\", \"should I start a LinkedIn newsletter\", \"grow my following\", \"90-day plan\". Validates the positioning brief, sizes the week against real hours and refuses a plan that will not survive week five, and gates a newsletter against eligibility and a six-month cadence commitment.","ibada0410\u002FCLAUDE-SKILLS","ibada0410","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F237597776?v=4","01M7EQWAZNCZV6Y4AGVBXWV5CD","Ibad Ahmed","01M7EQWB08BHXD7VT182EBQDCF",0,"MIT","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FSocial-Media-and-Content-Creation\u002Flinkedin-strategy\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: linkedin-strategy\ndescription: Use when someone needs a LinkedIn plan rather than a post — content pillars, positioning for a career change or consulting or thought leadership, a sustainable posting cadence, or a newsletter decision. Triggers on \"what should I post about\", \"how often should I post\", \"LinkedIn content strategy\", \"should I start a LinkedIn newsletter\", \"grow my following\", \"90-day plan\". Validates the positioning brief, sizes the week against real hours and refuses a plan that will not survive week five, and gates a newsletter against eligibility and a six-month cadence commitment.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-08-25\n---\n\n# LinkedIn Strategy — brief, cadence, newsletter\n\nThree decisions, in this order. Out of order is why most LinkedIn efforts produce a feed of\nunrelated observations and stop in week five.\n\n## Workflow\n\n**1. The brief — an editorial constitution, not a wish.** Walk the five questions one at a\ntime, each with a recommended answer, then validate:\n\n```bash\npython3 scripts\u002Fpositioning_brief.py --input brief.json --output human\n```\n\nIt refuses on the two things that make everything downstream impossible: an objective that\nis not one of the six real ones (`career-change`, `consulting`, `thought-leadership`,\n`hiring`, `fundraising`, `community`), and an audience too broad to exclude anyone. It also\nrefuses fewer than two exclusions — **a positioning that excludes nothing is availability.**\n\nPillars: two to four, shares summing to 100, at least one backed by proof that already\nexists, at least one at 10-20% as the experimental slot. Every pillar needs a \"why you\"; if\nanyone could post it, cut it.\n\nThe script emits observable 90-day criteria. Follower count is deliberately absent — it moves\nfor reasons unrelated to whether the objective is being met.\n\n**2. The cadence — priced against a bad week.**\n\n```bash\npython3 scripts\u002Fcadence_planner.py --minutes 240 --stage starting --target-posts 3 --output human\n```\n\nExit 0 fits \u002F 2 below the 90-minute floor \u002F 3 over budget with the overage named. Every\nactivity is priced in minutes including the reply window, which is part of the post and not\nan extra. Allocation shifts with stage: from a standing start **60% of the budget belongs in\nother people's comment sections**, because a post published to nobody reaches nobody.\n\nBelow 90 minutes a week it refuses to plan a posting schedule and returns a comment-only\nweek: a cadence abandoned in week five is worse than one never started, because the\nabandonment is visible on the profile. Every plan ships with a minimum viable week.\n\n**3. The newsletter — only if the promise can be paid.**\n\n```bash\npython3 scripts\u002Fnewsletter_planner.py --followers 1800 --cadence biweekly \\\n  --minutes-per-month 420 --pillar \"...\" --output human\n```\n\nRefuses below LinkedIn's published 150-follower evaluation floor, and refuses a cadence\nwhose six-month cost exceeds the budget. Emits a 12-issue arc rotating issue types across\npillars, and a stop rule written before issue one.\n\n## Rules\n\n- **One objective.** Two objectives serve neither; the audiences overlap less than they look.\n- **The exclusion list is the positioning.** Refuse to skip it.\n- **Price the week from a bad week, not a good one.**\n- **Consistency over volume.** A skipped week is fine; a skipped month resets you.\n- **Review the brief quarterly, not weekly.** A brief revised monthly is a mood.\n\n## Scripts\n\n| Script | Role |\n|---|---|\n| [`scripts\u002Fpositioning_brief.py`](scripts\u002Fpositioning_brief.py) | Validates objective, audience, 2-4 proof-backed pillars, and the exclusion list; emits observable 90-day criteria. |\n| [`scripts\u002Fcadence_planner.py`](scripts\u002Fcadence_planner.py) | Prices the week in minutes, allocates by stage, refuses over-budget targets, emits the minimum viable week. |\n| [`scripts\u002Fnewsletter_planner.py`](scripts\u002Fnewsletter_planner.py) | Eligibility + six-month sustainability gate, 12-issue arc across pillars, stop rule. |\n\n## References and assets\n\n- [`references\u002Fobjective_to_pillars.md`](references\u002Fobjective_to_pillars.md) — the six objectives and the pillar arithmetic (7 sources)\n- [`references\u002Fcadence_and_consistency.md`](references\u002Fcadence_and_consistency.md) — what a post really costs and why the floor exists (7 sources)\n- [`references\u002Fnewsletter_playbook.md`](references\u002Fnewsletter_playbook.md) — eligibility, cadence as a promise, the stop rule (7 sources)\n\n- [`assets\u002Fpositioning_brief_template.md`](assets\u002Fpositioning_brief_template.md) — fillable brief\n- [`assets\u002Fexample_brief.json`](assets\u002Fexample_brief.json) — a passing brief, for the validator\n\n## Distinct from\n\n- **`linkedin-content`** — drafts and lints individual posts. This decides what they are about\n  and how many there are. Posts without pillars are noise; offer this first, never chain silently.\n- **`linkedin-analytics`** — tells you what happened. This decides what to do next.\n- **`marketing-skill\u002Fcontent-strategy`** — company-level content marketing. This is one\n  person's own presence.\n\n---\n\n**Version:** 1.0.0\n","# LinkedIn Strategy — brief, cadence, newsletter\n\nThree decisions, in this order. Out of order is why most LinkedIn efforts produce a feed of\nunrelated observations and stop in week five.\n\n## Workflow\n\n**1. The brief — an editorial constitution, not a wish.** Walk the five questions one at a\ntime, each with a recommended answer, then validate:\n\n```bash\npython3 scripts\u002Fpositioning_brief.py --input brief.json --output human\n```\n\nIt refuses on the two things that make everything downstream impossible: an objective that\nis not one of the six real ones (`career-change`, `consulting`, `thought-leadership`,\n`hiring`, `fundraising`, `community`), and an audience too broad to exclude anyone. It also\nrefuses fewer than two exclusions — **a positioning that excludes nothing is availability.**\n\nPillars: two to four, shares summing to 100, at least one backed by proof that already\nexists, at least one at 10-20% as the experimental slot. Every pillar needs a \"why you\"; if\nanyone could post it, cut it.\n\nThe script emits observable 90-day criteria. Follower count is deliberately absent — it moves\nfor reasons unrelated to whether the objective is being met.\n\n**2. The cadence — priced against a bad week.**\n\n```bash\npython3 scripts\u002Fcadence_planner.py --minutes 240 --stage starting --target-posts 3 --output human\n```\n\nExit 0 fits \u002F 2 below the 90-minute floor \u002F 3 over budget with the overage named. Every\nactivity is priced in minutes including the reply window, which is part of the post and not\nan extra. Allocation shifts with stage: from a standing start **60% of the budget belongs in\nother people's comment sections**, because a post published to nobody reaches nobody.\n\nBelow 90 minutes a week it refuses to plan a posting schedule and returns a comment-only\nweek: a cadence abandoned in week five is worse than one never started, because the\nabandonment is visible on the profile. Every plan ships with a minimum viable week.\n\n**3. The newsletter — only if the promise can be paid.**\n\n```bash\npython3 scripts\u002Fnewsletter_planner.py --followers 1800 --cadence biweekly \\\n  --minutes-per-month 420 --pillar \"...\" --output human\n```\n\nRefuses below LinkedIn's published 150-follower evaluation floor, and refuses a cadence\nwhose six-month cost exceeds the budget. Emits a 12-issue arc rotating issue types across\npillars, and a stop rule written before issue one.\n\n## Rules\n\n- **One objective.** Two objectives serve neither; the audiences overlap less than they look.\n- **The exclusion list is the positioning.** Refuse to skip it.\n- **Price the week from a bad week, not a good one.**\n- **Consistency over volume.** A skipped week is fine; a skipped month resets you.\n- **Review the brief quarterly, not weekly.** A brief revised monthly is a mood.\n\n## Scripts\n\n| Script | Role |\n|---|---|\n| [`scripts\u002Fpositioning_brief.py`](scripts\u002Fpositioning_brief.py) | Validates objective, audience, 2-4 proof-backed pillars, and the exclusion list; emits observable 90-day criteria. |\n| [`scripts\u002Fcadence_planner.py`](scripts\u002Fcadence_planner.py) | Prices the week in minutes, allocates by stage, refuses over-budget targets, emits the minimum viable week. |\n| [`scripts\u002Fnewsletter_planner.py`](scripts\u002Fnewsletter_planner.py) | Eligibility + six-month sustainability gate, 12-issue arc across pillars, stop rule. |\n\n## References and assets\n\n- [`references\u002Fobjective_to_pillars.md`](references\u002Fobjective_to_pillars.md) — the six objectives and the pillar arithmetic (7 sources)\n- [`references\u002Fcadence_and_consistency.md`](references\u002Fcadence_and_consistency.md) — what a post really costs and why the floor exists (7 sources)\n- [`references\u002Fnewsletter_playbook.md`](references\u002Fnewsletter_playbook.md) — eligibility, cadence as a promise, the stop rule (7 sources)\n\n- [`assets\u002Fpositioning_brief_template.md`](assets\u002Fpositioning_brief_template.md) — fillable brief\n- [`assets\u002Fexample_brief.json`](assets\u002Fexample_brief.json) — a passing brief, for the validator\n\n## Distinct from\n\n- **`linkedin-content`** — drafts and lints individual posts. This decides what they are about\n  and how many there are. Posts without pillars are noise; offer this first, never chain silently.\n- **`linkedin-analytics`** — tells you what happened. This decides what to do next.\n- **`marketing-skill\u002Fcontent-strategy`** — company-level content marketing. This is one\n  person's own presence.\n\n---\n\n**Version:** 1.0.0\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"updated":26,"version":27,"category":28},"Alireza Rezvani",1787616000000,"1.0.0","marketing","main","26a049c61e6bda33cca8f5e7c1fcdcd20681221f","Social-Media-and-Content-Creation\u002Flinkedin-strategy","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS","https:\u002F\u002Fgithub.com\u002Fibada0410","2026-10-15 17:21:48",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add ibada0410\u002FCLAUDE-SKILLS --skill linkedin-strategy",{"tool":41,"command":42},"bunx","bunx skills add ibada0410\u002FCLAUDE-SKILLS --skill linkedin-strategy",{"tool":44,"command":45},"pnpm","pnpm dlx skills add ibada0410\u002FCLAUDE-SKILLS --skill linkedin-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FSocial-Media-and-Content-Creation\u002Flinkedin-strategy\u002FSKILL.md",true,[49,55,59,65,69,73,79,83],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"assets\u002Fexample_brief.json","ASSET","资产文件",1512,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FSocial-Media-and-Content-Creation\u002Flinkedin-strategy\u002Fassets\u002Fexample_brief.json",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"assets\u002Fpositioning_brief_template.md",2734,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FSocial-Media-and-Content-Creation\u002Flinkedin-strategy\u002Fassets\u002Fpositioning_brief_template.md",{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fcadence_and_consistency.md","REFERENCE","参考文档",5589,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FSocial-Media-and-Content-Creation\u002Flinkedin-strategy\u002Freferences\u002Fcadence_and_consistency.md",{"path":66,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fnewsletter_playbook.md",5955,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FSocial-Media-and-Content-Creation\u002Flinkedin-strategy\u002Freferences\u002Fnewsletter_playbook.md",{"path":70,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fobjective_to_pillars.md",6242,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FSocial-Media-and-Content-Creation\u002Flinkedin-strategy\u002Freferences\u002Fobjective_to_pillars.md",{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002Fcadence_planner.py","SCRIPT","脚本",11639,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FSocial-Media-and-Content-Creation\u002Flinkedin-strategy\u002Fscripts\u002Fcadence_planner.py",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"scripts\u002Fnewsletter_planner.py",11691,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FSocial-Media-and-Content-Creation\u002Flinkedin-strategy\u002Fscripts\u002Fnewsletter_planner.py",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"scripts\u002Fpositioning_brief.py",14356,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FSocial-Media-and-Content-Creation\u002Flinkedin-strategy\u002Fscripts\u002Fpositioning_brief.py",[88,97,105,113,121,129],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":92,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7F0YW5WXY39G4W3203E8PHN","internal-comms","A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Finternal-comms\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Finternal-comms\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7F0YGDEVB7BCSJX8V91XK15","eu-ai-act-reviewer","Review user journeys, public content, and codebases for potentially relevant EU AI Act provisions, with exact official citations, evidence gaps, application dates, and plain-language next actions. Use for EU AI Act issue-spotting, not final legal or compliance decisions.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Feu-ai-act-reviewer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Feu-ai-act-reviewer\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":92,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7F0Y1GYY34HD1WM5EWYB80Z","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Fdiscernment-nudge\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":92,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M7F0W4SJJY8Z345JZH9901RD","academy-guide","Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: \"how do I\", \"how can I\", \"getting started with\", \"what can Claude do\", \"teach me\", \"learn to use\"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Facademy-guide\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Facademy-guide\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":92,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":19},"01M7F0W0X5YSTSFS77CFA5P5KJ","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\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FUI-and-Web-Design\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FUI-and-Web-Design\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":92,"licenseFileUrl":133,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":19},"01M7F0VV4P1HYHG44P0K48C4Q7","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\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FUI-and-Web-Design\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FUI-and-Web-Design\u002Fweb-artifacts-builder\u002FSKILL.md",[],[]]