[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7APD6QCQT50HSZRH2S0TRH9":3,"skill-same:01M7APD6QCQT50HSZRH2S0TRH9":49},{"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":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7APD6QCQT50HSZRH2S0TRH9","configure-ecc",null,"Guide ECC installation, update, or reconfiguration from inside Claude Code, Codex, or Kimi while respecting each harness's real plugin, scope, and hook capabilities.","Cyrilthetecchieee\u002Fcyril-code-","Cyrilthetecchieee","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219787998?v=4","01M7AF0MMMKRAA0H61XMJPV92H","Julian Cyril D ","01M7AF0MQ10AVG6QJQ1C2BC0F5",2,"MIT","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fskills\u002Fconfigure-ecc\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: configure-ecc\ndescription: Guide ECC installation, update, or reconfiguration from inside Claude Code, Codex, or Kimi while respecting each harness's real plugin, scope, and hook capabilities.\nmetadata:\n  origin: ECC\n---\n\n# Configure Everything Claude Code\n\nRun a conversational wizard inside the current harness. Inventory first, collect\nonly supported choices, preview, confirm once, apply non-interactively, verify,\nand show the welcome only after success. Never clone ECC into a temporary\ndirectory or copy plugin components by hand.\n\nFor a human-operated terminal, the canonical entry points are `ecc setup` and\n`npx ecc-universal setup`. Inside a harness, use the explicit non-interactive\ncommands below instead.\n\n## Route by the current harness\n\n- In Claude Code, use the full scope-and-hook wizard below.\n- In Codex, use Codex's native plugin lifecycle. Do not offer Claude scopes or\n  map ECC's four Claude hook profiles onto Codex.\n- In Kimi, install the project surface under `.\u002F.kimi-code`. Kimi does not\n  provide ECC's Claude lifecycle-hook profiles.\n- If the harness is uncertain, state the detected evidence and ask which\n  harness to configure before running a mutating command.\n\nThis skill is a post-install reconfiguration path. It cannot intercept or\nreplace a provider's built-in first-install UI.\n\n## Claude Code: run the full conversational wizard\n\n### 1. Inventory without changing anything\n\nRun both commands and summarize the installed ECC scope, enabled state, and\nmarketplace source:\n\n```bash\nclaude plugin list --json\nclaude plugin marketplace list --json\n```\n\nTreat a single existing `ecc@ecc` installation as a reconfiguration. Do not\ninterpret Claude's provider-owned \"Open home page\" control as installation\nevidence. Stop and report the recovery returned by setup for multiple ECC\nscopes, a legacy\u002Fmanual install, malformed settings, or a marketplace collision;\nnever guess which state to delete.\n\n### 2. Collect exactly two choices\n\nAsk exactly one scope question and require one value:\n\n- `user | project | local`\n- `user` is global for this user.\n- `project` is shared through repository settings.\n- `local` is private to the current project.\n\nVisually mark only the selected scope as selected or installing. If the user\nchooses a different scope from a single existing install, describe it as a\nscope migration and include `--move-scope` in the commands below.\n\nAsk exactly one hook-mode question and require one value:\n\n- `off | minimal | standard | strict`\n- `off` keeps skills and commands but disables ECC hook automation.\n- `minimal` enables the lightest lifecycle and safety automation.\n- `standard` balances quality and safety automation.\n- `strict` enables the strongest checks and reminders.\n\nHook preference is personal Claude plugin configuration; it does not follow\nthe selected install scope.\n\n### 3. Preview and confirm once\n\nPrefer the plugin-bundled setup script. Substitute the two selected values and\ninclude `--move-scope` only for a scope migration:\n\n```bash\nnode \"$CLAUDE_PLUGIN_ROOT\u002Fscripts\u002Fsetup.js\" --mode claude-plugin \\\n  --scope \u003Cscope> --hooks \u003Chooks> [--move-scope] --dry-run --json\n```\n\nIf `$CLAUDE_PLUGIN_ROOT` is unavailable, use the published npm package:\n\n```bash\nnpx --yes --package ecc-universal ecc setup --mode claude-plugin \\\n  --scope \u003Cscope> --hooks \u003Chooks> [--move-scope] --dry-run --json\n```\n\nShow exactly one confirmation summary containing the planned action, one scope,\none hook mode, marketplace action, and any source-to-destination migration.\nAsk one yes\u002Fno question. Do not run a bare interactive `ecc setup` through a\nharness shell tool because that shell is commonly non-TTY.\n\n### 4. Apply the explicit choices\n\nAfter confirmation, rerun the same route without `--dry-run`. Keep every choice\nexplicit and request JSON so success can be checked deterministically:\n\n```bash\nnode \"$CLAUDE_PLUGIN_ROOT\u002Fscripts\u002Fsetup.js\" --mode claude-plugin \\\n  --scope \u003Cscope> --hooks \u003Chooks> [--move-scope] --yes --json\n```\n\nFallback:\n\n```bash\nnpx --yes --package ecc-universal ecc setup --mode claude-plugin \\\n  --scope \u003Cscope> --hooks \u003Chooks> [--move-scope] --yes --json\n```\n\n### 5. Verify, then render the welcome\n\nRequire a zero exit status and a setup result whose `scope` and `hooks` equal\nthe selected values. Then independently run:\n\n```bash\nclaude plugin list --json\n```\n\nContinue only when exactly one enabled `ecc@ecc` entry exists at the selected\nscope. When `$CLAUDE_PLUGIN_ROOT` is available, pass the successful setup\n`action` (`installed`, `updated`, `migrated`, `resumed`, or\n`already-migrated`) to the bundled renderer:\n\nBefore invoking it, require the provider-reported version to match\n`ECC_VERSION_PATTERN` from `scripts\u002Flib\u002Fterminal-welcome.js`. Reject unexpected\nversion text instead of interpolating it into a shell command.\n\n```bash\nnode -e 'const { renderTerminalWelcome } = require(process.env.CLAUDE_PLUGIN_ROOT + \"\u002Fscripts\u002Flib\u002Fterminal-welcome\"); process.stdout.write(renderTerminalWelcome({ action: process.argv[1], version: process.argv[2], color: process.stdout.isTTY }));' \"\u003Caction>\" \"\u003Cinstalled-version>\"\n```\n\nRender the welcome exactly once. On failure, dry-run, cancellation, a scope or\nhook mismatch, or unverifiable state, do not render it; report the error and\nrecovery instead. After verified changes, tell the user to run\n`\u002Freload-plugins` or restart Claude Code.\n\n## Codex: use the native plugin lifecycle\n\nInventory with `codex plugin marketplace list --json` and\n`codex plugin list --available --json`. Codex's native plugin command has no\nClaude-style `user | project | local` selector. Codex native plugins do support\nprovider-specific hooks, but Codex requires explicit trust for them. Let Codex\nshow that trust decision; do not ask the Claude four-profile hook question or\nclaim those profiles map to Codex.\n\nIf the ECC marketplace is missing, add it. Otherwise refresh its snapshot:\n\n```bash\ncodex plugin marketplace add affaan-m\u002FECC\ncodex plugin marketplace upgrade ecc --json\n```\n\nAsk for one confirmation, then install or idempotently refresh the installed\ncache and verify it:\n\n```bash\ncodex plugin add ecc@ecc --json\ncodex plugin list --json\n```\n\nContinue only when the JSON reports ECC installed and provides its\n`installedPath`. Then render the verified bundle's welcome:\n\nUse only the exact absolute `installedPath` returned by Codex JSON. Reject\ncontrol characters and require the installed version to match\n`ECC_VERSION_PATTERN`. Invoke `node` directly with this argument array; this is\na tool API invocation, not a shell command:\n\n```text\n[\"\u003CinstalledPath>\u002Fscripts\u002Fwelcome.js\", \"--action\", \"configured\", \"--version\", \"\u003Cinstalled-version>\"]\n```\n\nIf the current harness cannot invoke an executable with a separate argument\narray, skip the welcome. Never construct a shell command from Codex JSON values.\n\nNever claim that Claude's `off | minimal | standard | strict` profiles were\napplied to Codex.\n\n## Kimi: install the project surface\n\nState the capability summary before confirmation: destination\n`.\u002F.kimi-code`; `hooks=unsupported` for ECC lifecycle hooks. Do not ask the\nClaude scope or hook-mode questions. Preview first:\n\n```bash\nnpx --yes --package ecc-universal ecc install --profile core --target kimi --dry-run\n```\n\nShow one confirmation for that project destination, then apply the identical\ncommand without `--dry-run`. Verify with:\n\n```bash\nnpx --yes --package ecc-universal ecc doctor --target kimi\n```\n\nOnly after doctor succeeds and the installed instructions and skills remain\ninside `.\u002F.kimi-code`, render:\n\n```bash\nnpx --yes --package ecc-universal ecc welcome --action configured\n```\n\nDo not claim that Kimi installed or configured ECC lifecycle hooks.\n","# Configure Everything Claude Code\n\nRun a conversational wizard inside the current harness. Inventory first, collect\nonly supported choices, preview, confirm once, apply non-interactively, verify,\nand show the welcome only after success. Never clone ECC into a temporary\ndirectory or copy plugin components by hand.\n\nFor a human-operated terminal, the canonical entry points are `ecc setup` and\n`npx ecc-universal setup`. Inside a harness, use the explicit non-interactive\ncommands below instead.\n\n## Route by the current harness\n\n- In Claude Code, use the full scope-and-hook wizard below.\n- In Codex, use Codex's native plugin lifecycle. Do not offer Claude scopes or\n  map ECC's four Claude hook profiles onto Codex.\n- In Kimi, install the project surface under `.\u002F.kimi-code`. Kimi does not\n  provide ECC's Claude lifecycle-hook profiles.\n- If the harness is uncertain, state the detected evidence and ask which\n  harness to configure before running a mutating command.\n\nThis skill is a post-install reconfiguration path. It cannot intercept or\nreplace a provider's built-in first-install UI.\n\n## Claude Code: run the full conversational wizard\n\n### 1. Inventory without changing anything\n\nRun both commands and summarize the installed ECC scope, enabled state, and\nmarketplace source:\n\n```bash\nclaude plugin list --json\nclaude plugin marketplace list --json\n```\n\nTreat a single existing `ecc@ecc` installation as a reconfiguration. Do not\ninterpret Claude's provider-owned \"Open home page\" control as installation\nevidence. Stop and report the recovery returned by setup for multiple ECC\nscopes, a legacy\u002Fmanual install, malformed settings, or a marketplace collision;\nnever guess which state to delete.\n\n### 2. Collect exactly two choices\n\nAsk exactly one scope question and require one value:\n\n- `user | project | local`\n- `user` is global for this user.\n- `project` is shared through repository settings.\n- `local` is private to the current project.\n\nVisually mark only the selected scope as selected or installing. If the user\nchooses a different scope from a single existing install, describe it as a\nscope migration and include `--move-scope` in the commands below.\n\nAsk exactly one hook-mode question and require one value:\n\n- `off | minimal | standard | strict`\n- `off` keeps skills and commands but disables ECC hook automation.\n- `minimal` enables the lightest lifecycle and safety automation.\n- `standard` balances quality and safety automation.\n- `strict` enables the strongest checks and reminders.\n\nHook preference is personal Claude plugin configuration; it does not follow\nthe selected install scope.\n\n### 3. Preview and confirm once\n\nPrefer the plugin-bundled setup script. Substitute the two selected values and\ninclude `--move-scope` only for a scope migration:\n\n```bash\nnode \"$CLAUDE_PLUGIN_ROOT\u002Fscripts\u002Fsetup.js\" --mode claude-plugin \\\n  --scope \u003Cscope> --hooks \u003Chooks> [--move-scope] --dry-run --json\n```\n\nIf `$CLAUDE_PLUGIN_ROOT` is unavailable, use the published npm package:\n\n```bash\nnpx --yes --package ecc-universal ecc setup --mode claude-plugin \\\n  --scope \u003Cscope> --hooks \u003Chooks> [--move-scope] --dry-run --json\n```\n\nShow exactly one confirmation summary containing the planned action, one scope,\none hook mode, marketplace action, and any source-to-destination migration.\nAsk one yes\u002Fno question. Do not run a bare interactive `ecc setup` through a\nharness shell tool because that shell is commonly non-TTY.\n\n### 4. Apply the explicit choices\n\nAfter confirmation, rerun the same route without `--dry-run`. Keep every choice\nexplicit and request JSON so success can be checked deterministically:\n\n```bash\nnode \"$CLAUDE_PLUGIN_ROOT\u002Fscripts\u002Fsetup.js\" --mode claude-plugin \\\n  --scope \u003Cscope> --hooks \u003Chooks> [--move-scope] --yes --json\n```\n\nFallback:\n\n```bash\nnpx --yes --package ecc-universal ecc setup --mode claude-plugin \\\n  --scope \u003Cscope> --hooks \u003Chooks> [--move-scope] --yes --json\n```\n\n### 5. Verify, then render the welcome\n\nRequire a zero exit status and a setup result whose `scope` and `hooks` equal\nthe selected values. Then independently run:\n\n```bash\nclaude plugin list --json\n```\n\nContinue only when exactly one enabled `ecc@ecc` entry exists at the selected\nscope. When `$CLAUDE_PLUGIN_ROOT` is available, pass the successful setup\n`action` (`installed`, `updated`, `migrated`, `resumed`, or\n`already-migrated`) to the bundled renderer:\n\nBefore invoking it, require the provider-reported version to match\n`ECC_VERSION_PATTERN` from `scripts\u002Flib\u002Fterminal-welcome.js`. Reject unexpected\nversion text instead of interpolating it into a shell command.\n\n```bash\nnode -e 'const { renderTerminalWelcome } = require(process.env.CLAUDE_PLUGIN_ROOT + \"\u002Fscripts\u002Flib\u002Fterminal-welcome\"); process.stdout.write(renderTerminalWelcome({ action: process.argv[1], version: process.argv[2], color: process.stdout.isTTY }));' \"\u003Caction>\" \"\u003Cinstalled-version>\"\n```\n\nRender the welcome exactly once. On failure, dry-run, cancellation, a scope or\nhook mismatch, or unverifiable state, do not render it; report the error and\nrecovery instead. After verified changes, tell the user to run\n`\u002Freload-plugins` or restart Claude Code.\n\n## Codex: use the native plugin lifecycle\n\nInventory with `codex plugin marketplace list --json` and\n`codex plugin list --available --json`. Codex's native plugin command has no\nClaude-style `user | project | local` selector. Codex native plugins do support\nprovider-specific hooks, but Codex requires explicit trust for them. Let Codex\nshow that trust decision; do not ask the Claude four-profile hook question or\nclaim those profiles map to Codex.\n\nIf the ECC marketplace is missing, add it. Otherwise refresh its snapshot:\n\n```bash\ncodex plugin marketplace add affaan-m\u002FECC\ncodex plugin marketplace upgrade ecc --json\n```\n\nAsk for one confirmation, then install or idempotently refresh the installed\ncache and verify it:\n\n```bash\ncodex plugin add ecc@ecc --json\ncodex plugin list --json\n```\n\nContinue only when the JSON reports ECC installed and provides its\n`installedPath`. Then render the verified bundle's welcome:\n\nUse only the exact absolute `installedPath` returned by Codex JSON. Reject\ncontrol characters and require the installed version to match\n`ECC_VERSION_PATTERN`. Invoke `node` directly with this argument array; this is\na tool API invocation, not a shell command:\n\n```text\n[\"\u003CinstalledPath>\u002Fscripts\u002Fwelcome.js\", \"--action\", \"configured\", \"--version\", \"\u003Cinstalled-version>\"]\n```\n\nIf the current harness cannot invoke an executable with a separate argument\narray, skip the welcome. Never construct a shell command from Codex JSON values.\n\nNever claim that Claude's `off | minimal | standard | strict` profiles were\napplied to Codex.\n\n## Kimi: install the project surface\n\nState the capability summary before confirmation: destination\n`.\u002F.kimi-code`; `hooks=unsupported` for ECC lifecycle hooks. Do not ask the\nClaude scope or hook-mode questions. Preview first:\n\n```bash\nnpx --yes --package ecc-universal ecc install --profile core --target kimi --dry-run\n```\n\nShow one confirmation for that project destination, then apply the identical\ncommand without `--dry-run`. Verify with:\n\n```bash\nnpx --yes --package ecc-universal ecc doctor --target kimi\n```\n\nOnly after doctor succeeds and the installed instructions and skills remain\ninside `.\u002F.kimi-code`, render:\n\n```bash\nnpx --yes --package ecc-universal ecc welcome --action configured\n```\n\nDo not claim that Kimi installed or configured ECC lifecycle hooks.\n",{"name":5,"metadata":24,"description":7},{"origin":25},"ECC","main","57e7aa6b6e03bce1a7d7862ba9c2ec312f7f19b5","src\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fskills\u002Fconfigure-ecc",0,"https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee","https:\u002F\u002Fwithcyril.me\u002F","Hi, I’m Julian Cyril D, a Computer Science and Business Systems student at PSNACET.\r\nI’m passionate about full-stack development, UI\u002FUX design, and building sma","2026-11-04 23:28:50",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Cyrilthetecchieee\u002Fcyril-code- --skill configure-ecc",{"tool":41,"command":42},"bunx","bunx skills add Cyrilthetecchieee\u002Fcyril-code- --skill configure-ecc",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Cyrilthetecchieee\u002Fcyril-code- --skill configure-ecc","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fskills\u002Fconfigure-ecc\u002FSKILL.md",true,[],[50,59,66,74,81,88],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":54,"licenseFileUrl":55,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7AQV6CYX8RMC78420V9WZ62","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.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7AQV2895N3S1MEX6K76G6G2","youtube-downloader","Download YouTube videos with customizable quality and format options. Use this skill when the user asks to download, save, or grab YouTube videos. Supports various quality settings (best, 1080p, 720p, 480p, 360p), multiple formats (mp4, webm, mkv), and audio-only downloads as MP3.","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fvideo-downloader\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":54,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7AQTRNX62DNKVZ5GXEHRBKB","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Ftheme-factory\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7AQTNNVHAAN9H6DA8T6ZVE0","template-skill","Replace with description of the skill and when Claude should use it.","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Ftemplate-skill\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7AQTJ3MQ6AKX152MEX2MYCC","tailored-resume-generator","Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Ftailored-resume-generator\u002FSKILL.md",[],[],{"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":54,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7AQTD7D5MYET2YWG7HG9WM3","slack-gif-creator","Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives. This skill applies when users request animated GIFs or emoji animations for Slack from descriptions like \"make me a GIF for Slack of X doing Y\".","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fslack-gif-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fslack-gif-creator\u002FSKILL.md",[],[]]