[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77W6HEJ7ESFYTFRZF1C2FZ2":3,"skill-same:01M77W6HEJ7ESFYTFRZF1C2FZ2":68},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77W6HEJ7ESFYTFRZF1C2FZ2","security-review",null,"AI-powered codebase security scanner that reasons about code like a security researcher — tracing data flows, understanding component interactions, and catching vulnerabilities that pattern-matching tools miss. Use this skill when asked to scan code for security vulnerabilities, find bugs, check for SQL injection, XSS, command injection, exposed API keys, hardcoded secrets, insecure dependencies, access control issues, or any request like \"is my code secure?\", \"review for security issues\", \"audit this codebase\", or \"check for vulnerabilities\". Covers injection flaws, authentication and access control bugs, secrets exposure, weak cryptography, insecure dependencies, and business logic issues across JavaScript, TypeScript, Python, Java, PHP, Go, Ruby, and Rust.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"AI-powered codebase security scanner that reasons about code like a security researcher — tracing data flows, understanding component interactions, and catching vulnerabilities that pattern-matching tools miss. Use this skill when asked to scan code for security vulnerabilities, find bugs, check for SQL injection, XSS, command injection, exposed API keys, hardcoded secrets, insecure dependencies, access control issues, or any request like \\\"is my code secure?\\\", \\\"review for security issues\\\", \\\"audit this codebase\\\", or \\\"check for vulnerabilities\\\". Covers injection flaws, authentication and access control bugs, secrets exposure, weak cryptography, insecure dependencies, and business logic issues across JavaScript, TypeScript, Python, Java, PHP, Go, Ruby, and Rust.\"\n---\n# Security Review\n\nAn AI-powered security scanner that reasons about your codebase the way a human security\nresearcher would — tracing data flows, understanding component interactions, and catching\nvulnerabilities that pattern-matching tools miss.\n\n## When to Use This Skill\n\nUse this skill when the request involves:\n\n- Scanning a codebase or file for security vulnerabilities\n- Running a security review or vulnerability check\n- Checking for SQL injection, XSS, command injection, or other injection flaws\n- Finding exposed API keys, hardcoded secrets, or credentials in code\n- Auditing dependencies for known CVEs\n- Reviewing authentication, authorization, or access control logic\n- Detecting insecure cryptography or weak randomness\n- Performing a data flow analysis to trace user input to dangerous sinks\n- Any request phrasing like \"is my code secure?\", \"scan this file\", or \"check my repo for vulnerabilities\"\n- Running `\u002Fsecurity-review` or `\u002Fsecurity-review \u003Cpath>`\n\n## How This Skill Works\n\nUnlike traditional static analysis tools that match patterns, this skill:\n1. **Reads code like a security researcher** — understanding context, intent, and data flow\n2. **Traces across files** — following how user input moves through your application\n3. **Self-verifies findings** — re-examines each result to filter false positives\n4. **Assigns severity ratings** — CRITICAL \u002F HIGH \u002F MEDIUM \u002F LOW \u002F INFO\n5. **Proposes targeted patches** — every finding includes a concrete fix\n6. **Requires human approval** — nothing is auto-applied; you always review first\n\n## Execution Workflow\n\nFollow these steps **in order** every time:\n\n### Step 1 — Scope Resolution\nDetermine what to scan:\n- If a path was provided (`\u002Fsecurity-review src\u002Fauth\u002F`), scan only that scope\n- If no path given, scan the **entire project** starting from the root\n- Identify the language(s) and framework(s) in use (check package.json, requirements.txt,\n  go.mod, Cargo.toml, pom.xml, Gemfile, composer.json, etc.)\n- Read `references\u002Flanguage-patterns.md` to load language-specific vulnerability patterns\n\n### Step 2 — Dependency Audit\nBefore scanning source code, audit dependencies first (fast wins):\n- **Node.js**: Check `package.json` + `package-lock.json` for known vulnerable packages\n- **Python**: Check `requirements.txt` \u002F `pyproject.toml` \u002F `Pipfile`\n- **Java**: Check `pom.xml` \u002F `build.gradle`\n- **Ruby**: Check `Gemfile.lock`\n- **Rust**: Check `Cargo.toml`\n- **Go**: Check `go.sum`\n- Flag packages with known CVEs, deprecated crypto libs, or suspiciously old pinned versions\n- Read `references\u002Fvulnerable-packages.md` for a curated watchlist\n\n### Step 3 — Secrets & Exposure Scan\nScan ALL files (including config, env, CI\u002FCD, Dockerfiles, IaC) for:\n- Hardcoded API keys, tokens, passwords, private keys\n- `.env` files accidentally committed\n- Secrets in comments or debug logs\n- Cloud credentials (AWS, GCP, Azure, Stripe, Twilio, etc.)\n- Database connection strings with credentials embedded\n- Read `references\u002Fsecret-patterns.md` for regex patterns and entropy heuristics to apply\n\n### Step 4 — Vulnerability Deep Scan\nThis is the core scan. Reason about the code — don't just pattern-match.\nRead `references\u002Fvuln-categories.md` for full details on each category.\n\n**Injection Flaws**\n- SQL Injection: raw queries with string interpolation, ORM misuse, second-order SQLi\n- XSS: unescaped output, dangerouslySetInnerHTML, innerHTML, template injection\n- Command Injection: exec\u002Fspawn\u002Fsystem with user input\n- LDAP, XPath, Header, Log injection\n\n**Authentication & Access Control**\n- Missing authentication on sensitive endpoints\n- Broken object-level authorization (BOLA\u002FIDOR)\n- JWT weaknesses (alg:none, weak secrets, no expiry validation)\n- Session fixation, missing CSRF protection\n- Privilege escalation paths\n- Mass assignment \u002F parameter pollution\n\n**Data Handling**\n- Sensitive data in logs, error messages, or API responses\n- Missing encryption at rest or in transit\n- Insecure deserialization\n- Path traversal \u002F directory traversal\n- XXE (XML External Entity) processing\n- SSRF (Server-Side Request Forgery)\n\n**Cryptography**\n- Use of MD5, SHA1, DES for security purposes\n- Hardcoded IVs or salts\n- Weak random number generation (Math.random() for tokens)\n- Missing TLS certificate validation\n\n**Business Logic**\n- Race conditions (TOCTOU)\n- Integer overflow in financial calculations\n- Missing rate limiting on sensitive endpoints\n- Predictable resource identifiers\n\n### Step 5 — Cross-File Data Flow Analysis\nAfter the per-file scan, perform a **holistic review**:\n- Trace user-controlled input from entry points (HTTP params, headers, body, file uploads)\n  all the way to sinks (DB queries, exec calls, HTML output, file writes)\n- Identify vulnerabilities that only appear when looking at multiple files together\n- Check for insecure trust boundaries between services or modules\n\n### Step 6 — Self-Verification Pass\nFor EACH finding:\n1. Re-read the relevant code with fresh eyes\n2. Ask: \"Is this actually exploitable, or is there sanitization I missed?\"\n3. Check if a framework or middleware already handles this upstream\n4. Downgrade or discard findings that aren't genuine vulnerabilities\n5. Assign final severity: CRITICAL \u002F HIGH \u002F MEDIUM \u002F LOW \u002F INFO\n\n### Step 7 — Generate Security Report\nOutput the full report in the format defined in `references\u002Freport-format.md`.\n\n### Step 8 — Propose Patches\nFor every CRITICAL and HIGH finding, generate a concrete patch:\n- Show the vulnerable code (before)\n- Show the fixed code (after)\n- Explain what changed and why\n- Preserve the original code style, variable names, and structure\n- Add a comment explaining the fix inline\n\nExplicitly state: **\"Review each patch before applying. Nothing has been changed yet.\"**\n\n## Severity Guide\n\n| Severity | Meaning | Example |\n|----------|---------|---------|\n| 🔴 CRITICAL | Immediate exploitation risk, data breach likely | SQLi, RCE, auth bypass |\n| 🟠 HIGH | Serious vulnerability, exploit path exists | XSS, IDOR, hardcoded secrets |\n| 🟡 MEDIUM | Exploitable with conditions or chaining | CSRF, open redirect, weak crypto |\n| 🔵 LOW | Best practice violation, low direct risk | Verbose errors, missing headers |\n| ⚪ INFO | Observation worth noting, not a vulnerability | Outdated dependency (no CVE) |\n\n## Output Rules\n\n- **Always** produce a findings summary table first (counts by severity)\n- **Never** auto-apply any patch — present patches for human review only\n- **Always** include a confidence rating per finding (High \u002F Medium \u002F Low)\n- **Group findings** by category, not by file\n- **Be specific** — include file path, line number, and the exact vulnerable code snippet\n- **Explain the risk** in plain English — what could an attacker do with this?\n- If the codebase is clean, say so clearly: \"No vulnerabilities found\" with what was scanned\n\n## Reference Files\n\nFor detailed detection guidance, load the following reference files as needed:\n\n- `references\u002Fvuln-categories.md` — Deep reference for every vulnerability category with detection signals, safe patterns, and escalation checkers\n  - Search patterns: `SQL injection`, `XSS`, `command injection`, `SSRF`, `BOLA`, `IDOR`, `JWT`, `CSRF`, `secrets`, `cryptography`, `race condition`, `path traversal`\n- `references\u002Fsecret-patterns.md` — Regex patterns, entropy-based detection, and CI\u002FCD secret risks\n  - Search patterns: `API key`, `token`, `private key`, `connection string`, `entropy`, `.env`, `GitHub Actions`, `Docker`, `Terraform`\n- `references\u002Flanguage-patterns.md` — Framework-specific vulnerability patterns for JavaScript, Python, Java, PHP, Go, Ruby, and Rust\n  - Search patterns: `Express`, `React`, `Next.js`, `Django`, `Flask`, `FastAPI`, `Spring Boot`, `PHP`, `Go`, `Rails`, `Rust`\n- `references\u002Fvulnerable-packages.md` — Curated CVE watchlist for npm, pip, Maven, Rubygems, Cargo, and Go modules\n  - Search patterns: `lodash`, `axios`, `jsonwebtoken`, `Pillow`, `log4j`, `nokogiri`, `CVE`\n- `references\u002Freport-format.md` — Structured output template for security reports with finding cards, dependency audit, secrets scan, and patch proposal formatting\n  - Search patterns: `report`, `format`, `template`, `finding`, `patch`, `summary`, `confidence`\n","# Security Review\n\nAn AI-powered security scanner that reasons about your codebase the way a human security\nresearcher would — tracing data flows, understanding component interactions, and catching\nvulnerabilities that pattern-matching tools miss.\n\n## When to Use This Skill\n\nUse this skill when the request involves:\n\n- Scanning a codebase or file for security vulnerabilities\n- Running a security review or vulnerability check\n- Checking for SQL injection, XSS, command injection, or other injection flaws\n- Finding exposed API keys, hardcoded secrets, or credentials in code\n- Auditing dependencies for known CVEs\n- Reviewing authentication, authorization, or access control logic\n- Detecting insecure cryptography or weak randomness\n- Performing a data flow analysis to trace user input to dangerous sinks\n- Any request phrasing like \"is my code secure?\", \"scan this file\", or \"check my repo for vulnerabilities\"\n- Running `\u002Fsecurity-review` or `\u002Fsecurity-review \u003Cpath>`\n\n## How This Skill Works\n\nUnlike traditional static analysis tools that match patterns, this skill:\n1. **Reads code like a security researcher** — understanding context, intent, and data flow\n2. **Traces across files** — following how user input moves through your application\n3. **Self-verifies findings** — re-examines each result to filter false positives\n4. **Assigns severity ratings** — CRITICAL \u002F HIGH \u002F MEDIUM \u002F LOW \u002F INFO\n5. **Proposes targeted patches** — every finding includes a concrete fix\n6. **Requires human approval** — nothing is auto-applied; you always review first\n\n## Execution Workflow\n\nFollow these steps **in order** every time:\n\n### Step 1 — Scope Resolution\nDetermine what to scan:\n- If a path was provided (`\u002Fsecurity-review src\u002Fauth\u002F`), scan only that scope\n- If no path given, scan the **entire project** starting from the root\n- Identify the language(s) and framework(s) in use (check package.json, requirements.txt,\n  go.mod, Cargo.toml, pom.xml, Gemfile, composer.json, etc.)\n- Read `references\u002Flanguage-patterns.md` to load language-specific vulnerability patterns\n\n### Step 2 — Dependency Audit\nBefore scanning source code, audit dependencies first (fast wins):\n- **Node.js**: Check `package.json` + `package-lock.json` for known vulnerable packages\n- **Python**: Check `requirements.txt` \u002F `pyproject.toml` \u002F `Pipfile`\n- **Java**: Check `pom.xml` \u002F `build.gradle`\n- **Ruby**: Check `Gemfile.lock`\n- **Rust**: Check `Cargo.toml`\n- **Go**: Check `go.sum`\n- Flag packages with known CVEs, deprecated crypto libs, or suspiciously old pinned versions\n- Read `references\u002Fvulnerable-packages.md` for a curated watchlist\n\n### Step 3 — Secrets & Exposure Scan\nScan ALL files (including config, env, CI\u002FCD, Dockerfiles, IaC) for:\n- Hardcoded API keys, tokens, passwords, private keys\n- `.env` files accidentally committed\n- Secrets in comments or debug logs\n- Cloud credentials (AWS, GCP, Azure, Stripe, Twilio, etc.)\n- Database connection strings with credentials embedded\n- Read `references\u002Fsecret-patterns.md` for regex patterns and entropy heuristics to apply\n\n### Step 4 — Vulnerability Deep Scan\nThis is the core scan. Reason about the code — don't just pattern-match.\nRead `references\u002Fvuln-categories.md` for full details on each category.\n\n**Injection Flaws**\n- SQL Injection: raw queries with string interpolation, ORM misuse, second-order SQLi\n- XSS: unescaped output, dangerouslySetInnerHTML, innerHTML, template injection\n- Command Injection: exec\u002Fspawn\u002Fsystem with user input\n- LDAP, XPath, Header, Log injection\n\n**Authentication & Access Control**\n- Missing authentication on sensitive endpoints\n- Broken object-level authorization (BOLA\u002FIDOR)\n- JWT weaknesses (alg:none, weak secrets, no expiry validation)\n- Session fixation, missing CSRF protection\n- Privilege escalation paths\n- Mass assignment \u002F parameter pollution\n\n**Data Handling**\n- Sensitive data in logs, error messages, or API responses\n- Missing encryption at rest or in transit\n- Insecure deserialization\n- Path traversal \u002F directory traversal\n- XXE (XML External Entity) processing\n- SSRF (Server-Side Request Forgery)\n\n**Cryptography**\n- Use of MD5, SHA1, DES for security purposes\n- Hardcoded IVs or salts\n- Weak random number generation (Math.random() for tokens)\n- Missing TLS certificate validation\n\n**Business Logic**\n- Race conditions (TOCTOU)\n- Integer overflow in financial calculations\n- Missing rate limiting on sensitive endpoints\n- Predictable resource identifiers\n\n### Step 5 — Cross-File Data Flow Analysis\nAfter the per-file scan, perform a **holistic review**:\n- Trace user-controlled input from entry points (HTTP params, headers, body, file uploads)\n  all the way to sinks (DB queries, exec calls, HTML output, file writes)\n- Identify vulnerabilities that only appear when looking at multiple files together\n- Check for insecure trust boundaries between services or modules\n\n### Step 6 — Self-Verification Pass\nFor EACH finding:\n1. Re-read the relevant code with fresh eyes\n2. Ask: \"Is this actually exploitable, or is there sanitization I missed?\"\n3. Check if a framework or middleware already handles this upstream\n4. Downgrade or discard findings that aren't genuine vulnerabilities\n5. Assign final severity: CRITICAL \u002F HIGH \u002F MEDIUM \u002F LOW \u002F INFO\n\n### Step 7 — Generate Security Report\nOutput the full report in the format defined in `references\u002Freport-format.md`.\n\n### Step 8 — Propose Patches\nFor every CRITICAL and HIGH finding, generate a concrete patch:\n- Show the vulnerable code (before)\n- Show the fixed code (after)\n- Explain what changed and why\n- Preserve the original code style, variable names, and structure\n- Add a comment explaining the fix inline\n\nExplicitly state: **\"Review each patch before applying. Nothing has been changed yet.\"**\n\n## Severity Guide\n\n| Severity | Meaning | Example |\n|----------|---------|---------|\n| 🔴 CRITICAL | Immediate exploitation risk, data breach likely | SQLi, RCE, auth bypass |\n| 🟠 HIGH | Serious vulnerability, exploit path exists | XSS, IDOR, hardcoded secrets |\n| 🟡 MEDIUM | Exploitable with conditions or chaining | CSRF, open redirect, weak crypto |\n| 🔵 LOW | Best practice violation, low direct risk | Verbose errors, missing headers |\n| ⚪ INFO | Observation worth noting, not a vulnerability | Outdated dependency (no CVE) |\n\n## Output Rules\n\n- **Always** produce a findings summary table first (counts by severity)\n- **Never** auto-apply any patch — present patches for human review only\n- **Always** include a confidence rating per finding (High \u002F Medium \u002F Low)\n- **Group findings** by category, not by file\n- **Be specific** — include file path, line number, and the exact vulnerable code snippet\n- **Explain the risk** in plain English — what could an attacker do with this?\n- If the codebase is clean, say so clearly: \"No vulnerabilities found\" with what was scanned\n\n## Reference Files\n\nFor detailed detection guidance, load the following reference files as needed:\n\n- `references\u002Fvuln-categories.md` — Deep reference for every vulnerability category with detection signals, safe patterns, and escalation checkers\n  - Search patterns: `SQL injection`, `XSS`, `command injection`, `SSRF`, `BOLA`, `IDOR`, `JWT`, `CSRF`, `secrets`, `cryptography`, `race condition`, `path traversal`\n- `references\u002Fsecret-patterns.md` — Regex patterns, entropy-based detection, and CI\u002FCD secret risks\n  - Search patterns: `API key`, `token`, `private key`, `connection string`, `entropy`, `.env`, `GitHub Actions`, `Docker`, `Terraform`\n- `references\u002Flanguage-patterns.md` — Framework-specific vulnerability patterns for JavaScript, Python, Java, PHP, Go, Ruby, and Rust\n  - Search patterns: `Express`, `React`, `Next.js`, `Django`, `Flask`, `FastAPI`, `Spring Boot`, `PHP`, `Go`, `Rails`, `Rust`\n- `references\u002Fvulnerable-packages.md` — Curated CVE watchlist for npm, pip, Maven, Rubygems, Cargo, and Go modules\n  - Search patterns: `lodash`, `axios`, `jsonwebtoken`, `Pillow`, `log4j`, `nokogiri`, `CVE`\n- `references\u002Freport-format.md` — Structured output template for security reports with finding cards, dependency audit, secrets scan, and patch proposal formatting\n  - Search patterns: `report`, `format`, `template`, `finding`, `patch`, `summary`, `confidence`\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fsecurity-review",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill security-review",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill security-review",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill security-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fsecurity-review\u002FSKILL.md",true,[46,52,56,60,64],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Flanguage-patterns.md","REFERENCE","参考文档",5341,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fsecurity-review\u002Freferences\u002Flanguage-patterns.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Freport-format.md",6780,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fsecurity-review\u002Freferences\u002Freport-format.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fsecret-patterns.md",3524,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fsecurity-review\u002Freferences\u002Fsecret-patterns.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fvuln-categories.md",7913,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fsecurity-review\u002Freferences\u002Fvuln-categories.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fvulnerable-packages.md",3979,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fsecurity-review\u002Freferences\u002Fvulnerable-packages.md",[69,76,83,90,97,104],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\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":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]