[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DP3P107GFQJ9NH1R9DBJCA":3,"skill-same:01M7DP3P107GFQJ9NH1R9DBJCA":65},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7DP3P107GFQJ9NH1R9DBJCA","ship-gate",null,"Pre-production audit that scans a codebase for security, database, deployment, code quality, AI\u002FLLM, dependency, frontend, and observability issues. Intercepts deploy commands and blocks until critical items pass. Stack-agnostic. Use for \"run ship gate\", \"am I ready to ship\", \"pre-launch audit\", \"can I deploy\", \"push to production\", \"go live checklist\", \"preflight check\". Not for CI\u002FCD setup or infra provisioning.","Prudhviraj101\u002FX_Agent","Prudhviraj101","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141725940?v=4","01M7DN1Y3RW3QD7692M89MPS3D","MALLA PRUDHVI RAJ S S N MURTHY","01M7DN1Y4A763ESFP16P13EE19",0,"MIT","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fengineering__ship-gate\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ship-gate\ndescription: >\n  Pre-production audit that scans a codebase for security, database,\n  deployment, code quality, AI\u002FLLM, dependency, frontend, and observability\n  issues. Intercepts deploy commands and blocks until critical items pass.\n  Stack-agnostic. Use for \"run ship gate\", \"am I ready to ship\",\n  \"pre-launch audit\", \"can I deploy\", \"push to production\", \"go live\n  checklist\", \"preflight check\". Not for CI\u002FCD setup or infra provisioning.\nlicense: MIT\nmetadata:\n  author: Rajaraman Arumugam\n  version: 1.0.0\n---\n\n# Ship Gate\n\nPre-production audit that scans a codebase and reports pass\u002Ffail\u002Fmanual\nacross 8 categories before anything ships.\n\n## Intercept Behavior\n\nWhen the user says \"push to production\", \"deploy\", \"ship it\", \"go live\",\nor similar deploy-intent phrases, do NOT proceed with deployment. Instead:\n\n1. Ask: \"Have you run the ship gate? Want me to scan now?\"\n2. If yes, run the full audit below.\n3. If the user says they already ran it, ask when. If more than 24 hours\n   ago or if code changed since, recommend re-running.\n\n## How It Works\n\n### Step 1: Detect Stack\n\nRun these checks in order to identify the project stack:\n\n```\nFramework detection:\n  package.json exists        -> Node.js project\n    \"next\" in dependencies   -> Next.js\n    \"react\" in dependencies  -> React (if not Next.js)\n    \"vue\" in dependencies    -> Vue\n    \"svelte\" in dependencies -> Svelte\n    \"astro\" in dependencies  -> Astro\n    \"express\" in dependencies -> Express\n    \"fastify\" in dependencies -> Fastify\n    \"hono\" in dependencies   -> Hono\n  requirements.txt or pyproject.toml -> Python project\n    \"django\" present         -> Django\n    \"flask\" present          -> Flask\n    \"fastapi\" present        -> FastAPI\n  go.mod exists              -> Go project\n  Cargo.toml exists          -> Rust project\n\nDatabase detection:\n  \"@supabase\u002Fsupabase-js\" in package.json -> Supabase\n  supabase\u002F directory exists              -> Supabase\n  \"prisma\" in dependencies                -> Prisma (check schema for DB type)\n  \"mongoose\" in dependencies              -> MongoDB\n  \"pg\" or \"postgres\" in dependencies      -> PostgreSQL\n  firebase.json or .firebaserc exists     -> Firebase\n\nDeploy target detection:\n  vercel.json or .vercel\u002F exists          -> Vercel\n  netlify.toml exists                     -> Netlify\n  Dockerfile exists                       -> Docker\u002FVPS\n  fly.toml exists                         -> Fly.io\n  railway.json exists                     -> Railway\n  .platform\u002Fapplications.yaml            -> Platform.sh\n\nAuth detection:\n  \"@clerk\" in dependencies                -> Clerk\n  \"next-auth\" in dependencies             -> NextAuth\n  \"@supabase\u002Fauth-helpers\" in deps        -> Supabase Auth\n  \"firebase\u002Fauth\" in imports              -> Firebase Auth\n\nAI\u002FLLM detection:\n  \"openai\" in dependencies                -> OpenAI\n  \"@anthropic-ai\u002Fsdk\" in dependencies     -> Claude API\n  \"@google\u002Fgenerative-ai\" in deps         -> Gemini\n```\n\nReport detected stack before proceeding. This determines which checks\nare relevant. Checks tagged with a specific stack in `references\u002Fchecks.md`\nare skipped if that stack is not detected.\n\n### Step 2: Run Automated Checks\n\nRun categories in this order: SEC, DB, CODE, DEP, AI, DEPLOY, FE, OBS.\nSecurity and database first because they produce the most critical findings.\n\nFor each category, run every auto-scannable check from\n`references\u002Fchecks.md` using the patterns in `references\u002Fpatterns.md`.\n\nReport progress after each category completes:\n```\n[1\u002F8] Security: 3 FAIL, 12 PASS, 3 SKIP\n[2\u002F8] Database: 1 FAIL, 5 PASS, 6 SKIP\n...\n```\n\nReport results as:\n- PASS: check passed\n- FAIL: issue found (with file path and line number)\n- SKIP: not applicable to this stack\n\n### Step 3: Manual Confirmation\n\nFor checks that cannot be automated (backup restore tested, rollback plan\nexists, staging test passed), present them as a checklist and ask the user\nto confirm each one.\n\n### Step 4: Verdict\n\nClassify results into three severities:\n- CRITICAL: must fix before shipping (secrets exposed, no auth on routes,\n  no HTTPS, SQL injection vectors, no RLS on Supabase tables)\n- HIGH: should fix before shipping (no error boundaries, no rate limiting,\n  console.logs in production, no pagination)\n- ADVISORY: recommended but not blocking (no OG tags, no custom 404,\n  no analytics, no SBOM)\n\nFinal output:\n\n```\nSHIP GATE REPORT\n================\nStack: Next.js + Supabase + Vercel\nScan time: 12s\n\nCRITICAL (3 items, must fix)\n  FAIL  [SEC-01] API key found in src\u002Flib\u002Fapi.ts:14\n  FAIL  [DB-07] RLS not enabled on \"profiles\" table\n  FAIL  [SEC-05] No CSRF protection on \u002Fapi\u002Fcheckout\n\nHIGH (5 items, should fix)\n  FAIL  [CODE-01] 12 console.log statements in production code\n  FAIL  [CODE-03] Empty catch block in src\u002Futils\u002Fauth.ts:45\n  FAIL  [DEP-04] 3 critical npm audit vulnerabilities\n  FAIL  [DEPLOY-05] No rollback plan documented\n  MANUAL [DEPLOY-06] Staging test not confirmed\n\nADVISORY (4 items, recommended)\n  FAIL  [FE-01] Missing OG meta tags\n  FAIL  [FE-03] No custom 404 page\n  PASS  [OBS-01] Error monitoring configured\n  SKIP  [AI-01] No AI\u002FLLM usage detected\n\nVERDICT: DO NOT SHIP (3 critical issues)\nFix critical items and re-run.\n```\n\nIf zero critical items remain, verdict is: CLEAR TO SHIP.\nIf only high items remain, verdict is: SHIP WITH CAUTION (acknowledge risks).\n\n## Categories\n\nEight categories, each with a code prefix. Full check details in\n`references\u002Fchecks.md`.\n\n| Prefix | Category | Auto | Manual | Tool |\n|--------|----------|------|--------|------|\n| SEC | Security | 15 | 3 | 0 |\n| DB | Database | 7 | 5 | 0 |\n| DEPLOY | Deployment | 3 | 8 | 0 |\n| CODE | Code Quality | 11 | 0 | 1 |\n| AI | AI\u002FLLM Security | 5 | 3 | 0 |\n| DEP | Dependencies | 5 | 0 | 1 |\n| FE | Frontend Quality | 7 | 3 | 0 |\n| OBS | Observability | 2 | 5 | 0 |\n\n## Scope\n\nThis skill audits. It does not fix. When it finds issues, it reports\nthem with file locations and remediation guidance. The user or another\nskill (systematic-debugging, backend-patterns, shadcn-stack) handles\nthe fix.\n\nThis skill does not:\n- Set up CI\u002FCD pipelines\n- Provision infrastructure\n- Configure monitoring tools\n- Run after deployment (it is pre-deploy only)\n\n## Integration Points\n\n- **karpathy-coder**: run ship-gate after karpathy-check passes — simplicity first, then production readiness\n- **adversarial-reviewer**: deep security review for items ship-gate flags as critical\n- **security-pen-testing**: penetration testing methodology for SEC-category findings\n- **code-reviewer**: general code quality review complements ship-gate's automated checks\n","# Ship Gate\n\nPre-production audit that scans a codebase and reports pass\u002Ffail\u002Fmanual\nacross 8 categories before anything ships.\n\n## Intercept Behavior\n\nWhen the user says \"push to production\", \"deploy\", \"ship it\", \"go live\",\nor similar deploy-intent phrases, do NOT proceed with deployment. Instead:\n\n1. Ask: \"Have you run the ship gate? Want me to scan now?\"\n2. If yes, run the full audit below.\n3. If the user says they already ran it, ask when. If more than 24 hours\n   ago or if code changed since, recommend re-running.\n\n## How It Works\n\n### Step 1: Detect Stack\n\nRun these checks in order to identify the project stack:\n\n```\nFramework detection:\n  package.json exists        -> Node.js project\n    \"next\" in dependencies   -> Next.js\n    \"react\" in dependencies  -> React (if not Next.js)\n    \"vue\" in dependencies    -> Vue\n    \"svelte\" in dependencies -> Svelte\n    \"astro\" in dependencies  -> Astro\n    \"express\" in dependencies -> Express\n    \"fastify\" in dependencies -> Fastify\n    \"hono\" in dependencies   -> Hono\n  requirements.txt or pyproject.toml -> Python project\n    \"django\" present         -> Django\n    \"flask\" present          -> Flask\n    \"fastapi\" present        -> FastAPI\n  go.mod exists              -> Go project\n  Cargo.toml exists          -> Rust project\n\nDatabase detection:\n  \"@supabase\u002Fsupabase-js\" in package.json -> Supabase\n  supabase\u002F directory exists              -> Supabase\n  \"prisma\" in dependencies                -> Prisma (check schema for DB type)\n  \"mongoose\" in dependencies              -> MongoDB\n  \"pg\" or \"postgres\" in dependencies      -> PostgreSQL\n  firebase.json or .firebaserc exists     -> Firebase\n\nDeploy target detection:\n  vercel.json or .vercel\u002F exists          -> Vercel\n  netlify.toml exists                     -> Netlify\n  Dockerfile exists                       -> Docker\u002FVPS\n  fly.toml exists                         -> Fly.io\n  railway.json exists                     -> Railway\n  .platform\u002Fapplications.yaml            -> Platform.sh\n\nAuth detection:\n  \"@clerk\" in dependencies                -> Clerk\n  \"next-auth\" in dependencies             -> NextAuth\n  \"@supabase\u002Fauth-helpers\" in deps        -> Supabase Auth\n  \"firebase\u002Fauth\" in imports              -> Firebase Auth\n\nAI\u002FLLM detection:\n  \"openai\" in dependencies                -> OpenAI\n  \"@anthropic-ai\u002Fsdk\" in dependencies     -> Claude API\n  \"@google\u002Fgenerative-ai\" in deps         -> Gemini\n```\n\nReport detected stack before proceeding. This determines which checks\nare relevant. Checks tagged with a specific stack in `references\u002Fchecks.md`\nare skipped if that stack is not detected.\n\n### Step 2: Run Automated Checks\n\nRun categories in this order: SEC, DB, CODE, DEP, AI, DEPLOY, FE, OBS.\nSecurity and database first because they produce the most critical findings.\n\nFor each category, run every auto-scannable check from\n`references\u002Fchecks.md` using the patterns in `references\u002Fpatterns.md`.\n\nReport progress after each category completes:\n```\n[1\u002F8] Security: 3 FAIL, 12 PASS, 3 SKIP\n[2\u002F8] Database: 1 FAIL, 5 PASS, 6 SKIP\n...\n```\n\nReport results as:\n- PASS: check passed\n- FAIL: issue found (with file path and line number)\n- SKIP: not applicable to this stack\n\n### Step 3: Manual Confirmation\n\nFor checks that cannot be automated (backup restore tested, rollback plan\nexists, staging test passed), present them as a checklist and ask the user\nto confirm each one.\n\n### Step 4: Verdict\n\nClassify results into three severities:\n- CRITICAL: must fix before shipping (secrets exposed, no auth on routes,\n  no HTTPS, SQL injection vectors, no RLS on Supabase tables)\n- HIGH: should fix before shipping (no error boundaries, no rate limiting,\n  console.logs in production, no pagination)\n- ADVISORY: recommended but not blocking (no OG tags, no custom 404,\n  no analytics, no SBOM)\n\nFinal output:\n\n```\nSHIP GATE REPORT\n================\nStack: Next.js + Supabase + Vercel\nScan time: 12s\n\nCRITICAL (3 items, must fix)\n  FAIL  [SEC-01] API key found in src\u002Flib\u002Fapi.ts:14\n  FAIL  [DB-07] RLS not enabled on \"profiles\" table\n  FAIL  [SEC-05] No CSRF protection on \u002Fapi\u002Fcheckout\n\nHIGH (5 items, should fix)\n  FAIL  [CODE-01] 12 console.log statements in production code\n  FAIL  [CODE-03] Empty catch block in src\u002Futils\u002Fauth.ts:45\n  FAIL  [DEP-04] 3 critical npm audit vulnerabilities\n  FAIL  [DEPLOY-05] No rollback plan documented\n  MANUAL [DEPLOY-06] Staging test not confirmed\n\nADVISORY (4 items, recommended)\n  FAIL  [FE-01] Missing OG meta tags\n  FAIL  [FE-03] No custom 404 page\n  PASS  [OBS-01] Error monitoring configured\n  SKIP  [AI-01] No AI\u002FLLM usage detected\n\nVERDICT: DO NOT SHIP (3 critical issues)\nFix critical items and re-run.\n```\n\nIf zero critical items remain, verdict is: CLEAR TO SHIP.\nIf only high items remain, verdict is: SHIP WITH CAUTION (acknowledge risks).\n\n## Categories\n\nEight categories, each with a code prefix. Full check details in\n`references\u002Fchecks.md`.\n\n| Prefix | Category | Auto | Manual | Tool |\n|--------|----------|------|--------|------|\n| SEC | Security | 15 | 3 | 0 |\n| DB | Database | 7 | 5 | 0 |\n| DEPLOY | Deployment | 3 | 8 | 0 |\n| CODE | Code Quality | 11 | 0 | 1 |\n| AI | AI\u002FLLM Security | 5 | 3 | 0 |\n| DEP | Dependencies | 5 | 0 | 1 |\n| FE | Frontend Quality | 7 | 3 | 0 |\n| OBS | Observability | 2 | 5 | 0 |\n\n## Scope\n\nThis skill audits. It does not fix. When it finds issues, it reports\nthem with file locations and remediation guidance. The user or another\nskill (systematic-debugging, backend-patterns, shadcn-stack) handles\nthe fix.\n\nThis skill does not:\n- Set up CI\u002FCD pipelines\n- Provision infrastructure\n- Configure monitoring tools\n- Run after deployment (it is pre-deploy only)\n\n## Integration Points\n\n- **karpathy-coder**: run ship-gate after karpathy-check passes — simplicity first, then production readiness\n- **adversarial-reviewer**: deep security review for items ship-gate flags as critical\n- **security-pen-testing**: penetration testing methodology for SEC-category findings\n- **code-reviewer**: general code quality review complements ship-gate's automated checks\n",{"name":5,"license":15,"metadata":24,"description":27},{"author":25,"version":26},"Rajaraman Arumugam","1.0.0","Pre-production audit that scans a codebase for security, database, deployment, code quality, AI\u002FLLM, dependency, frontend, and observability issues. Intercepts deploy commands and blocks until critical items pass. Stack-agnostic. Use for \"run ship gate\", \"am I ready to ship\", \"pre-launch audit\", \"can I deploy\", \"push to production\", \"go live checklist\", \"preflight check\". Not for CI\u002FCD setup or infra provisioning.\n","main","229636be8dd3adf33e35a2aa95b85dc022251d6b",".agents\u002Fskills\u002Falirezarezvani\u002Fengineering__ship-gate","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent","https:\u002F\u002Fgithub.com\u002FPrudhviraj101","B.Tech CSE (AI\u002FML) Student | Building practical software with AI 🚀 | AI\u002FML Developer | Building AI agents, intelligent automation & real-world software ","2026-10-02 21:19:59",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Prudhviraj101\u002FX_Agent --skill ship-gate",{"tool":41,"command":42},"bunx","bunx skills add Prudhviraj101\u002FX_Agent --skill ship-gate",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Prudhviraj101\u002FX_Agent --skill ship-gate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fengineering__ship-gate\u002FSKILL.md",true,[49,55,59],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fchecks.md","REFERENCE","参考文档",19088,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fengineering__ship-gate\u002Freferences\u002Fchecks.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fpatterns.md",16780,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fengineering__ship-gate\u002Freferences\u002Fpatterns.md",{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"scripts\u002Fship_gate_scanner.py","SCRIPT","脚本",50439,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fengineering__ship-gate\u002Fscripts\u002Fship_gate_scanner.py",[66,75,83,91,98,106],{"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":70,"licenseFileUrl":71,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7DQMKNKM6F5G21PPJNW3HR5","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\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebapp-testing\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":70,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7DQMF21V9VHCTVS8H5JFNJM","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\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\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":70,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7DQM8HREQ0DN1HV12K0W3VT","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\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-factory\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7DQM5J7B71CQ8EVHBXCCCN2","systematic-planning","Formulate crisp, executable multi-phase implementation plans for non-trivial features, refactors, and architectural migrations. Use before writing code on any task with multiple files, uncertain requirements, or breaking changes.","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsystematic-planning\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":70,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7DQKG6WREWGRRCKHCJS96Y1","slack-gif-creator","Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"make me a GIF of X doing Y for Slack.\"","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fslack-gif-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fslack-gif-creator\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":70,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7DQJY7AN1XCX6G3ACA5K4JH","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[]]