[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77M2SCDWN3EM0SF256GH5J3":3,"skill-same:01M77M2SCDWN3EM0SF256GH5J3":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},"01M77M2SCDWN3EM0SF256GH5J3","conventional-branch",null,"Create Git branches following the Conventional Branch specification (feature\u002F, bugfix\u002F, hotfix\u002F, release\u002F, chore\u002F). Use when creating a new branch, naming a branch, or checking whether a branch name complies with the spec.","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\u002F.agents\u002Fskills\u002Fconventional-branch\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: conventional-branch\ndescription: 'Create Git branches following the Conventional Branch specification (feature\u002F, bugfix\u002F, hotfix\u002F, release\u002F, chore\u002F). Use when creating a new branch, naming a branch, or checking whether a branch name complies with the spec.'\n---\n\n# Conventional Branch\n\nCreate Git branches that follow the [Conventional Branch](https:\u002F\u002Fconventional-branch.github.io) specification — a simple, consistent convention for naming Git branches.\n\n## Branch Name Format\n\n```\n\u003Ctype>\u002F\u003Cdescription>\n```\n\n### Branch Types\n\n| Type | Alias | Purpose |\n|------|-------|---------|\n| `feature\u002F` | `feat\u002F` | New features or enhancements |\n| `bugfix\u002F` | `fix\u002F` | Bug fixes |\n| `hotfix\u002F` | — | Urgent production fixes |\n| `release\u002F` | — | Release preparation (dots allowed in version: `release\u002Fv1.2.0`) |\n| `chore\u002F` | — | Non-code tasks (deps, docs, config) |\n\n### Trunk Branches\n\n`main`, `master`, and `develop` are trunk branches — they do not use a prefix. Never create new branches with the same names as trunk branches; branch off them instead.\n\n## Naming Rules\n\n- **Lowercase only** — no uppercase letters anywhere\n- **Alphanumerics, hyphens, and dots** — `a-z`, `0-9`, `-`, `.`\n- **Dots allowed only** in `release\u002F` version descriptions (e.g., `release\u002Fv1.2.0`)\n- **No underscores, spaces, or special characters**\n- **No consecutive hyphens** (`--`), **dots** (`..`), or **hyphen-dot adjacency** (`-.` or `.-`)\n- **No leading or trailing hyphens or dots** in the description\n\n## Valid Examples\n\n```\nmain\nmaster\ndevelop\nfeature\u002Fadd-login-page\nfeat\u002Fadd-login-page\nbugfix\u002Ffix-header-bug\nfix\u002Fheader-bug\nhotfix\u002Fsecurity-patch\nrelease\u002Fv1.2.0\nchore\u002Fupdate-dependencies\nfeature\u002Fissue-123-new-login\n```\n\n## Invalid Examples\n\n| Branch | Problem |\n|--------|---------|\n| `Feature\u002FAdd-Login` | Uppercase letters |\n| `feature\u002Fnew--login` | Consecutive hyphens |\n| `feature\u002F-new-login` | Leading hyphen |\n| `feature\u002Fnew-login-` | Trailing hyphen |\n| `release\u002Fv1.-2.0` | Hyphen adjacent to dot |\n| `fix\u002Fheader bug` | Space |\n| `fix\u002Fheader_bug` | Underscore |\n| `unknown\u002Fsome-task` | Unknown prefix type |\n\n## Description Guidelines\n\n- Use **kebab-case** with 2-5 words\n- Be descriptive but concise (~50 chars total)\n- Good: `add-oauth-login`, `fix-header-overflow`, `update-ci-config`\n- Bad: `fix-bug`, `new-feature`\n\n## Workflow\n\n**Follow these steps:**\n\n**Step 1 — Determine Branch Type**\n\nAsk the user (if not already clear):\n\n- **Branch type** — default to `feature` when uncertain\n- **Brief description** — what the branch is for\n\nIf the user mentions a ticket or issue number, include it in the description (e.g., `feature\u002Fissue-123-add-oauth`).\n\n**Step 2 — Validate the Name**\n\nCheck the assembled name against the **Naming Rules** above. If any rule fails, fix it:\n\n- Lowercase everything\n- Replace underscores and spaces with hyphens\n- Collapse consecutive hyphens\n- Strip leading\u002Ftrailing hyphens\n\n**Step 3 — Detect the Base Branch**\n\nDifferent repos use different trunk branches. Detect which one this repo uses:\n\n```bash\n# Prefer the remote's default branch\ngit symbolic-ref --short refs\u002Fremotes\u002Forigin\u002FHEAD 2>\u002Fdev\u002Fnull | sed 's|^origin\u002F||'\n```\n\nIf that returns nothing, check which trunk branch exists locally (priority order: `develop`, `main`, `master`):\n\n```bash\nfor b in develop main master; do\n  git show-ref --verify --quiet \"refs\u002Fheads\u002F$b\" && echo \"$b\" && break\ndone\n```\n\n**Step 4 — Create and Checkout**\n\n```bash\ngit checkout \u003Cbase>\ngit pull origin \u003Cbase>\ngit checkout -b \u003Ctype>\u002F\u003Cdescription>\n```\n\n**Step 5 — Confirm**\n\nTell the user:\n- The branch name that was created\n- That they are now on the new branch\n- Remind them: `git push -u origin \u003Cbranch-name>` when ready\n\n## Relationship with Conventional Commits\n\nConventional Branch complements [Conventional Commits](https:\u002F\u002Fwww.conventionalcommits.org):\n\n| Conventional Branch | Typical Conventional Commit |\n|---------------------|----------------------------|\n| `feature\u002Fadd-login` | `feat: add login page` |\n| `bugfix\u002Ffix-header` | `fix: header overflow on mobile` |\n| `chore\u002Fupdate-deps` | `chore: bump lodash to 5.0` |\n| `release\u002Fv1.2.0` | `chore: release v1.2.0` |\n\nAlign the branch type with commit types where possible (e.g., `feature\u002F*` branches with `feat:` commits).\n","# Conventional Branch\n\nCreate Git branches that follow the [Conventional Branch](https:\u002F\u002Fconventional-branch.github.io) specification — a simple, consistent convention for naming Git branches.\n\n## Branch Name Format\n\n```\n\u003Ctype>\u002F\u003Cdescription>\n```\n\n### Branch Types\n\n| Type | Alias | Purpose |\n|------|-------|---------|\n| `feature\u002F` | `feat\u002F` | New features or enhancements |\n| `bugfix\u002F` | `fix\u002F` | Bug fixes |\n| `hotfix\u002F` | — | Urgent production fixes |\n| `release\u002F` | — | Release preparation (dots allowed in version: `release\u002Fv1.2.0`) |\n| `chore\u002F` | — | Non-code tasks (deps, docs, config) |\n\n### Trunk Branches\n\n`main`, `master`, and `develop` are trunk branches — they do not use a prefix. Never create new branches with the same names as trunk branches; branch off them instead.\n\n## Naming Rules\n\n- **Lowercase only** — no uppercase letters anywhere\n- **Alphanumerics, hyphens, and dots** — `a-z`, `0-9`, `-`, `.`\n- **Dots allowed only** in `release\u002F` version descriptions (e.g., `release\u002Fv1.2.0`)\n- **No underscores, spaces, or special characters**\n- **No consecutive hyphens** (`--`), **dots** (`..`), or **hyphen-dot adjacency** (`-.` or `.-`)\n- **No leading or trailing hyphens or dots** in the description\n\n## Valid Examples\n\n```\nmain\nmaster\ndevelop\nfeature\u002Fadd-login-page\nfeat\u002Fadd-login-page\nbugfix\u002Ffix-header-bug\nfix\u002Fheader-bug\nhotfix\u002Fsecurity-patch\nrelease\u002Fv1.2.0\nchore\u002Fupdate-dependencies\nfeature\u002Fissue-123-new-login\n```\n\n## Invalid Examples\n\n| Branch | Problem |\n|--------|---------|\n| `Feature\u002FAdd-Login` | Uppercase letters |\n| `feature\u002Fnew--login` | Consecutive hyphens |\n| `feature\u002F-new-login` | Leading hyphen |\n| `feature\u002Fnew-login-` | Trailing hyphen |\n| `release\u002Fv1.-2.0` | Hyphen adjacent to dot |\n| `fix\u002Fheader bug` | Space |\n| `fix\u002Fheader_bug` | Underscore |\n| `unknown\u002Fsome-task` | Unknown prefix type |\n\n## Description Guidelines\n\n- Use **kebab-case** with 2-5 words\n- Be descriptive but concise (~50 chars total)\n- Good: `add-oauth-login`, `fix-header-overflow`, `update-ci-config`\n- Bad: `fix-bug`, `new-feature`\n\n## Workflow\n\n**Follow these steps:**\n\n**Step 1 — Determine Branch Type**\n\nAsk the user (if not already clear):\n\n- **Branch type** — default to `feature` when uncertain\n- **Brief description** — what the branch is for\n\nIf the user mentions a ticket or issue number, include it in the description (e.g., `feature\u002Fissue-123-add-oauth`).\n\n**Step 2 — Validate the Name**\n\nCheck the assembled name against the **Naming Rules** above. If any rule fails, fix it:\n\n- Lowercase everything\n- Replace underscores and spaces with hyphens\n- Collapse consecutive hyphens\n- Strip leading\u002Ftrailing hyphens\n\n**Step 3 — Detect the Base Branch**\n\nDifferent repos use different trunk branches. Detect which one this repo uses:\n\n```bash\n# Prefer the remote's default branch\ngit symbolic-ref --short refs\u002Fremotes\u002Forigin\u002FHEAD 2>\u002Fdev\u002Fnull | sed 's|^origin\u002F||'\n```\n\nIf that returns nothing, check which trunk branch exists locally (priority order: `develop`, `main`, `master`):\n\n```bash\nfor b in develop main master; do\n  git show-ref --verify --quiet \"refs\u002Fheads\u002F$b\" && echo \"$b\" && break\ndone\n```\n\n**Step 4 — Create and Checkout**\n\n```bash\ngit checkout \u003Cbase>\ngit pull origin \u003Cbase>\ngit checkout -b \u003Ctype>\u002F\u003Cdescription>\n```\n\n**Step 5 — Confirm**\n\nTell the user:\n- The branch name that was created\n- That they are now on the new branch\n- Remind them: `git push -u origin \u003Cbranch-name>` when ready\n\n## Relationship with Conventional Commits\n\nConventional Branch complements [Conventional Commits](https:\u002F\u002Fwww.conventionalcommits.org):\n\n| Conventional Branch | Typical Conventional Commit |\n|---------------------|----------------------------|\n| `feature\u002Fadd-login` | `feat: add login page` |\n| `bugfix\u002Ffix-header` | `fix: header overflow on mobile` |\n| `chore\u002Fupdate-deps` | `chore: bump lodash to 5.0` |\n| `release\u002Fv1.2.0` | `chore: release v1.2.0` |\n\nAlign the branch type with commit types where possible (e.g., `feature\u002F*` branches with `feat:` commits).\n",{"name":5,"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92",".agents\u002Fskills\u002Fconventional-branch",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 conventional-branch",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill conventional-branch",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill conventional-branch","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconventional-branch\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",[],[]]