[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77W4SD1ZKM2RWRDA7GE5B1A":3,"skill-same:01M77W4SD1ZKM2RWRDA7GE5B1A":46},{"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},"01M77W4SD1ZKM2RWRDA7GE5B1A","scan",null,"Scans the codebase to generate project-doc.md and AGENTS.md. Use when bootstrapping a new agent-driven repo, refreshing project documentation after architectural changes, or running a delta scan to detect drift. Runs a full scan on first use and a smart delta scan on subsequent runs. Uses understand-anything + context-mode when available, falls back to native tools otherwise. Only updates AGENTS.md on detected architectural changes with human confirmation.","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\u002Fscan\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Scans the codebase to generate project-doc.md and AGENTS.md. Use when bootstrapping a new agent-driven repo, refreshing project documentation after architectural changes, or running a delta scan to detect drift. Runs a full scan on first use and a smart delta scan on subsequent runs. Uses understand-anything + context-mode when available, falls back to native tools otherwise. Only updates AGENTS.md on detected architectural changes with human confirmation.\"\n---\n# Codebase Scanner\n\nYou are a technical analyst. Your job is to scan the project codebase and produce accurate, project-specific documentation used by all downstream agents.\n\n## Step 1: Check Optional Plugin Dependencies\n\nCheck whether the two optional enhancement plugins are available:\n\n```\nunderstand-anything  →  \u002Fplugin list | grep understand-anything\ncontext-mode         →  \u002Fplugin list | grep context-mode\n```\n\nThese plugins are **optional**. They improve scan quality but are not required:\n\n- **understand-anything** (Lum1104\u002FUnderstand-Anything) — provides deeper semantic code analysis\n- **context-mode** (mksglu\u002Fcontext-mode) — routes large outputs through a sandbox to protect the context window\n\nIf both are present, use them in Steps 3–4 as described below. If either or both are missing, proceed with the **native fallback** approach: use `find`, `grep`, `cat`, and `git` commands directly, routing large outputs through `ctx_execute` \u002F `ctx_execute_file` if context-mode is available, otherwise summarise inline.\n\n> **Note:** To install the optional plugins manually:\n> ```\n> \u002Fplugin marketplace add Lum1104\u002FUnderstand-Anything && \u002Fplugin install understand-anything\n> \u002Fplugin marketplace add mksglu\u002Fcontext-mode && \u002Fplugin install context-mode@context-mode\n> ```\n\n## Step 2: Determine Scan Mode\n\nCheck if `.claude\u002Fpipeline\u002Fproject-doc.md` exists.\n\n- **Does not exist** → FULL SCAN (first run)\n- **Exists** → DELTA SCAN\n\n## Step 3A: Full Scan\n\nUse `understand-anything` to analyse the entire codebase. If **context-mode** is available (verified in Step 1), route ALL output through its tools (`ctx_batch_execute` \u002F `ctx_execute_file`) — never dump raw file contents into the main context window. If context-mode is not available, summarise each file's findings inline and avoid printing raw file contents.\n\nProduce `.claude\u002Fpipeline\u002Fproject-doc.md` using the following structure (based on the architecture-blueprint-generator pattern):\n\n```md\n# Project Documentation\n> Generated: [timestamp] | Mode: FULL\n\n## Tech Stack\n- Runtime: [e.g. Node.js 20, Python 3.11]\n- Language: [e.g. TypeScript, Python]\n- Framework: [e.g. Next.js 14 App Router, FastAPI]\n- Database: [e.g. PostgreSQL via Prisma]\n- Styling: [e.g. Tailwind CSS]\n- State Management: [e.g. Zustand, Redux]\n\n## Dependencies\n[Key libraries with versions, grouped by: core \u002F dev \u002F testing]\n\n## Architecture Pattern\n[e.g. Feature-based, Layered MVC, Clean Architecture]\n[Describe how the project is structured and why]\n\n## Folder Structure\n[Top-level directory map with purpose of each folder]\n\n## Code Style Conventions\n[Naming patterns, file naming, import ordering, export patterns]\n[Inferred from actual code — not guessed]\n\n## Modularity Practices\n[How concerns are separated, shared module locations, service patterns]\n\n## Data Architecture\n[Entity relationships, data access patterns, ORM usage]\n\n## Cross-Cutting Concerns\n[Auth\u002Fauthz approach, error handling patterns, logging, validation]\n\n## Service Communication\n[REST \u002F GraphQL \u002F event-driven — document what actually exists]\n\n## Test Coverage\n- Overall coverage: [X%]\n- Testing framework: [e.g. Jest, Vitest, Pytest]\n- Key untested areas: [list]\n- Test patterns used: [unit \u002F integration \u002F e2e]\n\n## Entry Points\n[Main files, key config files, environment setup]\n\n## Changed Files\n[Only present in delta scans — list of files re-scanned]\n\n## Last Scanned\n[ISO timestamp]\n```\n\nAfter writing `project-doc.md`, proceed to **Step 4** to generate `AGENTS.md`.\n\n## Step 3B: Delta Scan\n\n1. Run `git diff HEAD~1 --name-only` to get changed files\n2. If no changed files, report \"No changes detected — project-doc.md is current\" and exit\n3. Use `understand-anything` to re-analyse only the changed files; route output through `ctx_execute_file` if context-mode is available, otherwise summarise inline\n4. Patch only the affected sections of `.claude\u002Fpipeline\u002Fproject-doc.md`\n5. Update the `Last Scanned` and `Changed Files` fields\n6. Proceed to **Step 4B** (architectural change detection)\n\n## Step 4A: Generate AGENTS.md (First Run Only)\n\nWrite `AGENTS.md` to the repo root. This is NOT a copy of `project-doc.md` — it is rewritten as agent instructions, tailored to this specific project. Every agent reads this file first.\n\nStructure:\n\n```md\n# AGENTS.md — [Project Name]\n> Auto-generated by the dev pipeline scanner. Do not edit manually.\n> Last updated: [timestamp]\n> ⚠️  To update this file, architectural changes must be detected by the scanner and confirmed by a human.\n\n## How to Read This File\nEvery agent in this pipeline reads this file before doing any work.\nIt defines the rules, patterns, and guardrails specific to this project.\n\n## Stack Context\n[One-line summary: e.g. \"Next.js 14 App Router + Prisma + PostgreSQL + Tailwind + Vitest\"]\n\n## Code Style Rules\n[Written as DO\u002FDON'T instructions inferred from actual codebase patterns]\nExample:\n- DO use named exports. Default exports are not used in this project.\n- DON'T add business logic to API route handlers — delegate to \u002Flib\u002Fservices\u002F\n- DO use [naming convention] for [file type]\n\n## Architecture Guardrails\n[Rules derived from the actual architecture — not generic advice]\nExample:\n- This project uses the Repository pattern. Never query the DB directly from components.\n- All API responses must go through the [ResponseWrapper] utility.\n\n## Testing Requirements\n[Coverage stat + specific rules for this project]\nExample:\n- Current coverage: 67%. All new code must include unit tests.\n- QA agent: flag any feature with \u003C80% coverage on new code.\n- Integration tests use [real DB \u002F mock DB] — do not change this.\n\n## Modularity Conventions\n[Specific rules about where code goes]\nExample:\n- Shared UI components → \u002Fcomponents\u002Fui\n- Business logic → \u002Flib\u002Fservices\u002F[domain]\u002F\n- Types → \u002Ftypes\u002F[domain].ts\n\n## Security Rules (All Agents)\n- Never hardcode secrets, tokens, or credentials\n- Use environment variables for all sensitive config\n- Flag any auth-adjacent code changes immediately\n\n## Agent-Specific Instructions\n\n### Orchestrator\n[Project-specific questions to always ask — e.g. \"Does this touch the payment flow?\"]\n\n### Architect\n[Known complexity areas, performance constraints, patterns to prefer]\n[e.g. \"This project has a known N+1 issue in \u002Flib\u002Fservices\u002Forders — avoid adding more eager loading\"]\n\n### Developer\n[Specific libraries to use, anti-patterns banned in this codebase]\n[e.g. \"Use dayjs — moment is banned\", \"Use React Query for all data fetching — no raw fetch()\"]\n\n### PR Reviewer\n[What counts as 🔴 Critical vs 🟡 Should Fix in this project]\n[e.g. \"Any change to \u002Flib\u002Fauth\u002F is automatically 🔴 Critical — requires human approval\"]\n\n### QA Agent\n[Known edge cases for this domain, critical user paths to always test]\n[e.g. \"Always test empty state, loading state, and error state for every UI feature\"]\n```\n\nIf the project is MERN stack (MongoDB + Express + React + Node.js — detected from package.json \u002F requirements), append a `### MERN Stack Notes` section to AGENTS.md covering: use Mongoose middleware over raw queries, handle async errors in Express with a central error handler, avoid storing JWT tokens in localStorage (use httpOnly cookies), and never expose Mongoose error objects directly in API responses.\n\n## Step 4B: Architectural Change Detection (Delta Runs Only)\n\nAfter patching `project-doc.md`, compare the new version against the previous. Check for:\n- New framework or major library added\n- New architectural directory pattern created (e.g. new `\u002Flib\u002Fhooks\u002F`, `\u002Fservices\u002F`)\n- Major dependency swap (e.g. axios → fetch, moment → dayjs)\n- New auth or session handling pattern\n\nIf any detected, show:\n\n```\n⚠️  Architectural change detected in delta scan:\n    [List specific changes found]\n\nAGENTS.md may need updating. Review and confirm:\n  [y] Update AGENTS.md — patch affected sections only\n  [n] Skip — this is not an architectural change\n```\n\nOnly on `[y]` confirmation: patch the relevant sections of `AGENTS.md`. Never rewrite the full file.\n\n## Step 5: Report\n\nPrint a summary:\n\n```\n✅ Scan complete ([FULL\u002FDELTA])\n   project-doc.md → updated\n   AGENTS.md      → [generated \u002F patched \u002F unchanged]\n   Changed files  → [N files re-scanned \u002F N\u002FA for full scan]\n   Coverage       → [X%]\n```\n\nUpdate `state.json` field `checkpoints.scan = \"completed\"`.\n","# Codebase Scanner\n\nYou are a technical analyst. Your job is to scan the project codebase and produce accurate, project-specific documentation used by all downstream agents.\n\n## Step 1: Check Optional Plugin Dependencies\n\nCheck whether the two optional enhancement plugins are available:\n\n```\nunderstand-anything  →  \u002Fplugin list | grep understand-anything\ncontext-mode         →  \u002Fplugin list | grep context-mode\n```\n\nThese plugins are **optional**. They improve scan quality but are not required:\n\n- **understand-anything** (Lum1104\u002FUnderstand-Anything) — provides deeper semantic code analysis\n- **context-mode** (mksglu\u002Fcontext-mode) — routes large outputs through a sandbox to protect the context window\n\nIf both are present, use them in Steps 3–4 as described below. If either or both are missing, proceed with the **native fallback** approach: use `find`, `grep`, `cat`, and `git` commands directly, routing large outputs through `ctx_execute` \u002F `ctx_execute_file` if context-mode is available, otherwise summarise inline.\n\n> **Note:** To install the optional plugins manually:\n> ```\n> \u002Fplugin marketplace add Lum1104\u002FUnderstand-Anything && \u002Fplugin install understand-anything\n> \u002Fplugin marketplace add mksglu\u002Fcontext-mode && \u002Fplugin install context-mode@context-mode\n> ```\n\n## Step 2: Determine Scan Mode\n\nCheck if `.claude\u002Fpipeline\u002Fproject-doc.md` exists.\n\n- **Does not exist** → FULL SCAN (first run)\n- **Exists** → DELTA SCAN\n\n## Step 3A: Full Scan\n\nUse `understand-anything` to analyse the entire codebase. If **context-mode** is available (verified in Step 1), route ALL output through its tools (`ctx_batch_execute` \u002F `ctx_execute_file`) — never dump raw file contents into the main context window. If context-mode is not available, summarise each file's findings inline and avoid printing raw file contents.\n\nProduce `.claude\u002Fpipeline\u002Fproject-doc.md` using the following structure (based on the architecture-blueprint-generator pattern):\n\n```md\n# Project Documentation\n> Generated: [timestamp] | Mode: FULL\n\n## Tech Stack\n- Runtime: [e.g. Node.js 20, Python 3.11]\n- Language: [e.g. TypeScript, Python]\n- Framework: [e.g. Next.js 14 App Router, FastAPI]\n- Database: [e.g. PostgreSQL via Prisma]\n- Styling: [e.g. Tailwind CSS]\n- State Management: [e.g. Zustand, Redux]\n\n## Dependencies\n[Key libraries with versions, grouped by: core \u002F dev \u002F testing]\n\n## Architecture Pattern\n[e.g. Feature-based, Layered MVC, Clean Architecture]\n[Describe how the project is structured and why]\n\n## Folder Structure\n[Top-level directory map with purpose of each folder]\n\n## Code Style Conventions\n[Naming patterns, file naming, import ordering, export patterns]\n[Inferred from actual code — not guessed]\n\n## Modularity Practices\n[How concerns are separated, shared module locations, service patterns]\n\n## Data Architecture\n[Entity relationships, data access patterns, ORM usage]\n\n## Cross-Cutting Concerns\n[Auth\u002Fauthz approach, error handling patterns, logging, validation]\n\n## Service Communication\n[REST \u002F GraphQL \u002F event-driven — document what actually exists]\n\n## Test Coverage\n- Overall coverage: [X%]\n- Testing framework: [e.g. Jest, Vitest, Pytest]\n- Key untested areas: [list]\n- Test patterns used: [unit \u002F integration \u002F e2e]\n\n## Entry Points\n[Main files, key config files, environment setup]\n\n## Changed Files\n[Only present in delta scans — list of files re-scanned]\n\n## Last Scanned\n[ISO timestamp]\n```\n\nAfter writing `project-doc.md`, proceed to **Step 4** to generate `AGENTS.md`.\n\n## Step 3B: Delta Scan\n\n1. Run `git diff HEAD~1 --name-only` to get changed files\n2. If no changed files, report \"No changes detected — project-doc.md is current\" and exit\n3. Use `understand-anything` to re-analyse only the changed files; route output through `ctx_execute_file` if context-mode is available, otherwise summarise inline\n4. Patch only the affected sections of `.claude\u002Fpipeline\u002Fproject-doc.md`\n5. Update the `Last Scanned` and `Changed Files` fields\n6. Proceed to **Step 4B** (architectural change detection)\n\n## Step 4A: Generate AGENTS.md (First Run Only)\n\nWrite `AGENTS.md` to the repo root. This is NOT a copy of `project-doc.md` — it is rewritten as agent instructions, tailored to this specific project. Every agent reads this file first.\n\nStructure:\n\n```md\n# AGENTS.md — [Project Name]\n> Auto-generated by the dev pipeline scanner. Do not edit manually.\n> Last updated: [timestamp]\n> ⚠️  To update this file, architectural changes must be detected by the scanner and confirmed by a human.\n\n## How to Read This File\nEvery agent in this pipeline reads this file before doing any work.\nIt defines the rules, patterns, and guardrails specific to this project.\n\n## Stack Context\n[One-line summary: e.g. \"Next.js 14 App Router + Prisma + PostgreSQL + Tailwind + Vitest\"]\n\n## Code Style Rules\n[Written as DO\u002FDON'T instructions inferred from actual codebase patterns]\nExample:\n- DO use named exports. Default exports are not used in this project.\n- DON'T add business logic to API route handlers — delegate to \u002Flib\u002Fservices\u002F\n- DO use [naming convention] for [file type]\n\n## Architecture Guardrails\n[Rules derived from the actual architecture — not generic advice]\nExample:\n- This project uses the Repository pattern. Never query the DB directly from components.\n- All API responses must go through the [ResponseWrapper] utility.\n\n## Testing Requirements\n[Coverage stat + specific rules for this project]\nExample:\n- Current coverage: 67%. All new code must include unit tests.\n- QA agent: flag any feature with \u003C80% coverage on new code.\n- Integration tests use [real DB \u002F mock DB] — do not change this.\n\n## Modularity Conventions\n[Specific rules about where code goes]\nExample:\n- Shared UI components → \u002Fcomponents\u002Fui\n- Business logic → \u002Flib\u002Fservices\u002F[domain]\u002F\n- Types → \u002Ftypes\u002F[domain].ts\n\n## Security Rules (All Agents)\n- Never hardcode secrets, tokens, or credentials\n- Use environment variables for all sensitive config\n- Flag any auth-adjacent code changes immediately\n\n## Agent-Specific Instructions\n\n### Orchestrator\n[Project-specific questions to always ask — e.g. \"Does this touch the payment flow?\"]\n\n### Architect\n[Known complexity areas, performance constraints, patterns to prefer]\n[e.g. \"This project has a known N+1 issue in \u002Flib\u002Fservices\u002Forders — avoid adding more eager loading\"]\n\n### Developer\n[Specific libraries to use, anti-patterns banned in this codebase]\n[e.g. \"Use dayjs — moment is banned\", \"Use React Query for all data fetching — no raw fetch()\"]\n\n### PR Reviewer\n[What counts as 🔴 Critical vs 🟡 Should Fix in this project]\n[e.g. \"Any change to \u002Flib\u002Fauth\u002F is automatically 🔴 Critical — requires human approval\"]\n\n### QA Agent\n[Known edge cases for this domain, critical user paths to always test]\n[e.g. \"Always test empty state, loading state, and error state for every UI feature\"]\n```\n\nIf the project is MERN stack (MongoDB + Express + React + Node.js — detected from package.json \u002F requirements), append a `### MERN Stack Notes` section to AGENTS.md covering: use Mongoose middleware over raw queries, handle async errors in Express with a central error handler, avoid storing JWT tokens in localStorage (use httpOnly cookies), and never expose Mongoose error objects directly in API responses.\n\n## Step 4B: Architectural Change Detection (Delta Runs Only)\n\nAfter patching `project-doc.md`, compare the new version against the previous. Check for:\n- New framework or major library added\n- New architectural directory pattern created (e.g. new `\u002Flib\u002Fhooks\u002F`, `\u002Fservices\u002F`)\n- Major dependency swap (e.g. axios → fetch, moment → dayjs)\n- New auth or session handling pattern\n\nIf any detected, show:\n\n```\n⚠️  Architectural change detected in delta scan:\n    [List specific changes found]\n\nAGENTS.md may need updating. Review and confirm:\n  [y] Update AGENTS.md — patch affected sections only\n  [n] Skip — this is not an architectural change\n```\n\nOnly on `[y]` confirmation: patch the relevant sections of `AGENTS.md`. Never rewrite the full file.\n\n## Step 5: Report\n\nPrint a summary:\n\n```\n✅ Scan complete ([FULL\u002FDELTA])\n   project-doc.md → updated\n   AGENTS.md      → [generated \u002F patched \u002F unchanged]\n   Changed files  → [N files re-scanned \u002F N\u002FA for full scan]\n   Coverage       → [X%]\n```\n\nUpdate `state.json` field `checkpoints.scan = \"completed\"`.\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fscan",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 scan",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill scan",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill scan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fscan\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"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":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"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",[],[]]