[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77WBM1539KNJMAT1ZDQZFVJ":3,"skill-same:01M77WBM1539KNJMAT1ZDQZFVJ":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},"01M77WBM1539KNJMAT1ZDQZFVJ","signal-write",null,"Emit structured agent signals — hands-up, blocked, done, checkpoint, partnership. Signals are written as JSON to .signals\u002F for dashboard consumption and noted in the journal for persistence.","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\u002Fsignal-write\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Emit structured agent signals — hands-up, blocked, done, checkpoint, partnership. Signals are written as JSON to .signals\u002F for dashboard consumption and noted in the journal for persistence.\"\n---\n# Agent Signals\n\nEmit structured signals from a desk to the operator or other desks.\n\n## When to use\n\n- A desk needs operator attention (hands-up, blocked)\n- Work is complete and ready for review (done)\n- Significant progress worth noting (checkpoint)\n- Two desks disagree and can't resolve it (hands-up)\n- The TA is reporting coordination quality (partnership)\n\n## Signal types\n\n### `hands-up`\nTwo desks disagree and can't settle it against external facts.\nThis is the system working — the operator reads where desks\n*disagree*, not where they perform confidence.\n\n### `blocked`\nA desk can't proceed without input — missing access, ambiguous\nscope, need a decision only the operator can make.\n\n### `done`\nWork is complete and ready for review. Artifacts are on the bench.\n\n### `checkpoint`\nSignificant progress worth the operator knowing about, but work\ncontinues. Not blocked, not done — just a marker.\n\n### `partnership`\nUsed by the TA (room coordinator) to report coordination quality.\nSelf-assessment scores reflect coordination, not code accuracy:\n- **intent** — understood what the operator needed\n- **confidence** — right work went to the right desks\n- **accuracy** — dispatched work produced the right outcome\n- **completeness** — nothing fell through the cracks\n\n## How to emit\n\n### 1. Write a JSON signal file to `.signals\u002F`\n\nThis is the primary output — it's what the dashboard reads.\nCreate `desks\u002F\u003Cdesk-name>\u002F.signals\u002F\u003Ctimestamp>.json`:\n\n```json\n{\n  \"signal_type\": \"execution\",\n  \"subtype\": \"checkpoint\",\n  \"timestamp\": \"2026-07-19T21:30:00Z\",\n  \"run_id\": \"\u003Coptional; set to pair this with an outcome signal>\",\n  \"agent_name\": \"\u003Cdesk-name>\",\n  \"self_assessment\": {\n    \"intent\": 4,\n    \"confidence\": 5,\n    \"accuracy\": 4,\n    \"completeness\": 3\n  },\n  \"patterns\": {\n    \"what_worked\": \"description of what went well\",\n    \"what_was_hard\": \"description of challenges\",\n    \"skill_gap\": \"areas for improvement\"\n  },\n  \"escalation\": {\n    \"reason\": null,\n    \"blocked_on\": null,\n    \"recommendation\": null\n  }\n}\n```\n\n### Signal type mapping\n\n| Signal    | `signal_type`   | `subtype`      |\n|-----------|-----------------|----------------|\n| hands-up  | `\"escalation\"`  | `\"hands-up\"`   |\n| blocked   | `\"escalation\"`  | `\"blocked\"`    |\n| done      | `\"execution\"`   | `\"done\"`       |\n| checkpoint| `\"execution\"`   | `\"checkpoint\"` |\n| partnership| `\"partnership\"` | `\"partnership\"`|\n\nThe `subtype` field preserves the specific signal state for\ndashboard consumers. `signal_type` controls sort priority\n(escalation → top).\n\n> **Note:** The signals-dashboard canvas extension reads `subtype`\n> when present and falls back to `signal_type` for display. If\n> consuming signals in your own tooling, prefer `subtype` for the\n> specific state.\n\n> **Ordering:** include a `timestamp` (ISO 8601 UTC). The dashboard\n> orders signals by it and falls back to file mtime only when it's\n> absent — a git clone\u002Fcheckout resets mtimes, so mtime alone is not a\n> dependable clock.\n\n### 2. Note the signal in the journal\n\nAlso append a short marker to the desk's journal for persistence:\n\n```markdown\n## \u003Cdate> — [signal:\u003Ctype>] \u003Csummary>\n- \u003Ckey details>\n```\n\nThe journal note is the trail marker. The JSON file is the\nmachine-readable signal.\n\n## Outcome signals (calibration)\n\nThe signals-dashboard can pair a desk's self-assessment with an\n*outcome* — an independent rating of the realized result — and show\nthe **honesty gap** (how far the desk's confidence was from the\ndelivered quality). Outcome signals are optional and are usually\nemitted by a reviewer\u002Fevaluator, not the desk itself.\n\nWrite them to the **same** `.signals\u002F` directory:\n\n```json\n{\n  \"signal_type\": \"outcome\",\n  \"run_id\": \"\u003Csame run_id as the signal it rates>\",\n  \"agent_name\": \"\u003Creviewer name>\",\n  \"quality_rating\": 4,\n  \"effort_to_merge\": \"minimal\",\n  \"issues_found\": [\"optional short strings\"],\n  \"timestamp\": \"2026-07-19T22:00:00Z\"\n}\n```\n\n- **`run_id`** correlates an outcome with the execution\u002Fpartnership\n  signal it rates — set the same `run_id` on both. If it's absent, the\n  dashboard falls back to the nearest outcome emitted shortly after the\n  latest signal.\n- **`quality_rating`** (0–5) is the realized quality; the dashboard\n  compares it to the desk's self-assessed `confidence` to compute the\n  honesty gap.\n- **`effort_to_merge`** — `\"minimal\"`, `\"moderate\"`, or `\"significant\"`.\n- **`issues_found`** — optional array of short strings.\n\n## Principles\n\n- Signals are structured, not chatty. Short, factual, actionable.\n- hands-up is not failure — it's the most valuable signal. It\n  means the system caught something one frame alone would have\n  missed.\n- Don't signal for routine progress. Signals are for state\n  changes that affect the room, not status updates.\n- blocked means truly blocked — not \"I'd prefer input.\" If you\n  can proceed with a reasonable default, proceed and note it.\n- Self-assessment scores should be honest, not optimistic. A 3\u002F5\n  is fine. A 5\u002F5 on everything is suspicious.\n","# Agent Signals\n\nEmit structured signals from a desk to the operator or other desks.\n\n## When to use\n\n- A desk needs operator attention (hands-up, blocked)\n- Work is complete and ready for review (done)\n- Significant progress worth noting (checkpoint)\n- Two desks disagree and can't resolve it (hands-up)\n- The TA is reporting coordination quality (partnership)\n\n## Signal types\n\n### `hands-up`\nTwo desks disagree and can't settle it against external facts.\nThis is the system working — the operator reads where desks\n*disagree*, not where they perform confidence.\n\n### `blocked`\nA desk can't proceed without input — missing access, ambiguous\nscope, need a decision only the operator can make.\n\n### `done`\nWork is complete and ready for review. Artifacts are on the bench.\n\n### `checkpoint`\nSignificant progress worth the operator knowing about, but work\ncontinues. Not blocked, not done — just a marker.\n\n### `partnership`\nUsed by the TA (room coordinator) to report coordination quality.\nSelf-assessment scores reflect coordination, not code accuracy:\n- **intent** — understood what the operator needed\n- **confidence** — right work went to the right desks\n- **accuracy** — dispatched work produced the right outcome\n- **completeness** — nothing fell through the cracks\n\n## How to emit\n\n### 1. Write a JSON signal file to `.signals\u002F`\n\nThis is the primary output — it's what the dashboard reads.\nCreate `desks\u002F\u003Cdesk-name>\u002F.signals\u002F\u003Ctimestamp>.json`:\n\n```json\n{\n  \"signal_type\": \"execution\",\n  \"subtype\": \"checkpoint\",\n  \"timestamp\": \"2026-07-19T21:30:00Z\",\n  \"run_id\": \"\u003Coptional; set to pair this with an outcome signal>\",\n  \"agent_name\": \"\u003Cdesk-name>\",\n  \"self_assessment\": {\n    \"intent\": 4,\n    \"confidence\": 5,\n    \"accuracy\": 4,\n    \"completeness\": 3\n  },\n  \"patterns\": {\n    \"what_worked\": \"description of what went well\",\n    \"what_was_hard\": \"description of challenges\",\n    \"skill_gap\": \"areas for improvement\"\n  },\n  \"escalation\": {\n    \"reason\": null,\n    \"blocked_on\": null,\n    \"recommendation\": null\n  }\n}\n```\n\n### Signal type mapping\n\n| Signal    | `signal_type`   | `subtype`      |\n|-----------|-----------------|----------------|\n| hands-up  | `\"escalation\"`  | `\"hands-up\"`   |\n| blocked   | `\"escalation\"`  | `\"blocked\"`    |\n| done      | `\"execution\"`   | `\"done\"`       |\n| checkpoint| `\"execution\"`   | `\"checkpoint\"` |\n| partnership| `\"partnership\"` | `\"partnership\"`|\n\nThe `subtype` field preserves the specific signal state for\ndashboard consumers. `signal_type` controls sort priority\n(escalation → top).\n\n> **Note:** The signals-dashboard canvas extension reads `subtype`\n> when present and falls back to `signal_type` for display. If\n> consuming signals in your own tooling, prefer `subtype` for the\n> specific state.\n\n> **Ordering:** include a `timestamp` (ISO 8601 UTC). The dashboard\n> orders signals by it and falls back to file mtime only when it's\n> absent — a git clone\u002Fcheckout resets mtimes, so mtime alone is not a\n> dependable clock.\n\n### 2. Note the signal in the journal\n\nAlso append a short marker to the desk's journal for persistence:\n\n```markdown\n## \u003Cdate> — [signal:\u003Ctype>] \u003Csummary>\n- \u003Ckey details>\n```\n\nThe journal note is the trail marker. The JSON file is the\nmachine-readable signal.\n\n## Outcome signals (calibration)\n\nThe signals-dashboard can pair a desk's self-assessment with an\n*outcome* — an independent rating of the realized result — and show\nthe **honesty gap** (how far the desk's confidence was from the\ndelivered quality). Outcome signals are optional and are usually\nemitted by a reviewer\u002Fevaluator, not the desk itself.\n\nWrite them to the **same** `.signals\u002F` directory:\n\n```json\n{\n  \"signal_type\": \"outcome\",\n  \"run_id\": \"\u003Csame run_id as the signal it rates>\",\n  \"agent_name\": \"\u003Creviewer name>\",\n  \"quality_rating\": 4,\n  \"effort_to_merge\": \"minimal\",\n  \"issues_found\": [\"optional short strings\"],\n  \"timestamp\": \"2026-07-19T22:00:00Z\"\n}\n```\n\n- **`run_id`** correlates an outcome with the execution\u002Fpartnership\n  signal it rates — set the same `run_id` on both. If it's absent, the\n  dashboard falls back to the nearest outcome emitted shortly after the\n  latest signal.\n- **`quality_rating`** (0–5) is the realized quality; the dashboard\n  compares it to the desk's self-assessed `confidence` to compute the\n  honesty gap.\n- **`effort_to_merge`** — `\"minimal\"`, `\"moderate\"`, or `\"significant\"`.\n- **`issues_found`** — optional array of short strings.\n\n## Principles\n\n- Signals are structured, not chatty. Short, factual, actionable.\n- hands-up is not failure — it's the most valuable signal. It\n  means the system caught something one frame alone would have\n  missed.\n- Don't signal for routine progress. Signals are for state\n  changes that affect the room, not status updates.\n- blocked means truly blocked — not \"I'd prefer input.\" If you\n  can proceed with a reasonable default, proceed and note it.\n- Self-assessment scores should be honest, not optimistic. A 3\u002F5\n  is fine. A 5\u002F5 on everything is suspicious.\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fsignal-write",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 signal-write",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill signal-write",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill signal-write","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fsignal-write\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",[],[]]