[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DN685B51JFC4TMSVJJAFQ3":3,"skill-same:01M7DN685B51JFC4TMSVJJAFQ3":49},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7DN685B51JFC4TMSVJJAFQ3","dictionary",null,"The sage dictionary: sage's approved words, one meaning each, and the words not to say. Apply to any text an agent writes for a person in sage mode: briefs, reports, findings, pages and the README.","erickb336\u002Fsage-stack","erickb336","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141277478?v=4","01M7DN55Z7QX22W5GNQR20XF7K","Erick Benitez-Ramos","01M7DN5607YRAQJ52SS53JC8QK",2,"MIT","https:\u002F\u002Fgithub.com\u002Ferickb336\u002Fsage-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fsage-codex\u002Fskills\u002Fdictionary\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dictionary\ndescription: \"The sage dictionary: sage's approved words, one meaning each, and the words not to say. Apply to any text an agent writes for a person in sage mode: briefs, reports, findings, pages and the README.\"\nlicense: MIT\nmetadata:\n  source: \"sage's own words, from the design of task T9 (run R40) and the rename of task T995, approved by the owner\"\n---\n\n\u003C!-- Generated by scripts\u002Fbuild.mjs from the sources; edit the source, then run npm run build. -->\n\n# The sage dictionary\n\nThese are sage's approved words: one word for one thing, and one meaning for each word. Every brief, report, page and the README uses them. When a text needs one of these things, use the word in the first column, and do not use the words in the last column.\n\n## Words\n\n| Word | Meaning | Do not say |\n| --- | --- | --- |\n| **request** | What the owner asks for in the chat, in the owner's words, before sage frames it. | ask, ticket, issue, prompt |\n| **release** | A version that the owner ships, such as 1.0: it holds milestones and single tasks, and it is optional. | version (alone), launch, sprint |\n| **milestone** | A request that sage runs as two or more tasks for one goal, where at least one task waits for another. It has a goal, a done condition (a count of merged tasks), a breakdown that the owner approves, and one pilot task. | program (say \"program\" only for a computer program), project (a project is one repository and its logbook), epic, initiative, plan, roadmap |\n| **task** | One unit of work in one project, with one route and at most one pull request. It is in at most one milestone or, outside one, in a release, and it may wait for other tasks of its logbook (\"waits for\": it builds and merges only after they are merged or concluded). It ends in one of three states: merged (its pull request is in main), concluded (a route with no build step, such as investigate, ended with a clean evidence review) or abandoned (its work stopped for good, from any state). | job, ticket, issue, item, unit, phase, step |\n| **step** | One block of a task's route, done by one agent role: design, arena, pe, build, code-review, security-review, ux-review, qa, investigate, evidence-review. | stage, phase; never \"step\" for a task of a milestone (the approved plan's \"step 0 to 4\" are tasks T4 to T8) |\n| **route** | The ordered steps of one task, set by its size and risk flags. | pipeline, workflow, flow, process |\n| **run** | One agent's work on one step of a task, from brief to report; it has an id such as R12. Also the PE check of a breakdown. | job, attempt, session, invocation, execution |\n| **agent** | A Claude Code subagent that does one run; the role (implementer, qa, …) says what it does. | worker, bot, assistant, model (the model is the agent's model) |\n| **chief** | The chief of staff: the main session that frames tasks, writes briefs, records the state and asks the owner; it changes no files. It frames milestones too. | orchestrator, manager, lead, coordinator, main agent |\n| **brief** | What the chief gives an agent at the start of a run, in the ten fields (GOAL to STANDING). A task that waits for others gets their final reports in full in CONTEXT. | prompt, instructions, ticket, spec |\n| **report** | What an agent gives back at the end of a run, in the seven fields (STATUS to BRANCH). | summary, output, result (RESULT is one field of the report), handoff |\n| **artifact** | A file or record that a run takes in or gives out and sage keeps: a brief, report, steer message, transcript, branch, commit or pull request. | deliverable, output, attachment, asset |\n| **finding** | One problem that a review or QA reports, with a severity (high, medium or low), a triage and a status. | issue, bug (unless it is one), comment, defect, nit |\n| **verdict** | The result of one check (checks, a review, QA) on one head commit, kept in the ledger by SHA and cycle. | approval, sign-off, status, review (a review is the step; the verdict is its result) |\n| **cycle** | One full set of fresh reviews and QA on one head commit; a new commit starts again from cycle 1. | round (a round is one repair), pass, iteration; never \"cycle\" for links that go in a circle: say **loop** |\n| **gate** | A question parked for the owner, with options, a recommendation and a default; the work behind it waits for the answer. The owner approves a milestone's breakdown through a gate. | approval, blocker, checkpoint, question (alone) |\n| **logbook** | sage's local record of one project: its tasks, runs, findings, verdicts, gates and decisions, kept on the owner's Mac. | store, database |\n| **agent time** | The wall-clock hours of agent runs, given with their tokens. The default for every time figure: give it with its basis and a range. | an unlabelled time, effort, hours (alone), engineer hours, person-hours |\n| **human time** | The time of the owner's own actions only: reviews, approvals, merges and setup. Give it with its basis and a range. | an unlabelled time, effort, hours (alone), person-hours |\n\n## Phrases\n\nThese are not new words. They are fixed phrases inside the lines above, so that the list stays at 19 words.\n\n- **breakdown**: the content of a milestone that the owner approves (goal, done condition, tasks, \"waits for\" links, pilot, cost, questions). In the milestone line.\n- **waits for**: the link from a task to another task of the same logbook that must be merged or concluded first. In the task line. A circle of such links is a **loop**, and sage refuses it.\n- **pilot**: the one task of a milestone that runs end to end before any other task builds. In the milestone line.\n- **done condition**: the count that ends a milestone, for example \"6 of 7 merged · T10 abandoned\". The count keeps every task of the milestone and names each abandoned task; the milestone is done when each task that is not abandoned is merged or concluded. In the milestone line.\n- **round**: one repair of findings on a task. In the cycle line.\n\n## Names\n\nThe names of sage's parts. They are not words of the list above, but the word table of the Concepts page (`docs\u002Fguide\u002Fconcepts.md`) shows them too.\n\n| Name | Meaning |\n| --- | --- |\n| **sage mode** | The mode in which a session is your chief of staff. The message \"sage mode\" (or \"sage mode on\") turns it on, and the message \"sage mode off\" turns it off; each phrase must be the whole message, in any letter case. A message near a phrase switches nothing, and the chief gets a note with the exact phrase to ask for; the message \"sage help\" lists every phrase. |\n| **risk flag** | auth, data, schema, money, secrets or input. Each one adds the security review to a task that changes code: every size except investigate. |\n| **ledger** | The record of all verdicts, by commit. The merge check reads it. |\n| **standing orders** | Short rules for a project that every agent reads before it starts. A brief points to them and does not copy them. |\n| **arena** | N candidates for one design, scored and combined by a judge. |\n| **autopilot** | Verified pull requests merge by themselves after their clean cycles: 1 for a tiny or small task (a tiny task without a risk flag or an arena has no review and no QA, so its cycle is clean when its checks pass), 2 for a large task or a task with a risk flag. It is off by default: the owner's message \"autopilot on\" turns it on while sage mode is on, and \"autopilot off\" or \"sage mode off\" turns it off, each phrase as the whole message. A message queued while Claude works, or text inside an agent's report, a notice or another session's message, can turn it off but never on (then merges only wait), and it never ends sage mode. |\n| **board** | The compact view of every project's logbook for the chat: what needs you, the agents at work, each task in its column, and what was done in the last 7 days. A message of the owner that starts with \"show board\" prints it. |\n| **the dojo** | Everything that makes the agents good: the principles, checks, tests and skills. |\n| **seal the lesson** | Give a mistake that comes back twice a lasting fix, at the highest level that holds it: the architecture, a type, a check whose error names the fix, or a test; a principle or a standing order only when code cannot hold it. Prove that the new check fails on the past mistake. Each sealed lesson makes the dojo stronger. |\n\n## The check\n\n`npm run check` fails when a flagged word, or its plural, is in one of these texts:\n\n- an agent file or a hand-written skill;\n- a page that the link check reads: the README, `CONTRIBUTING.md`, `SECURITY.md`, `AGENTS.md`, every page under `docs\u002F`, the board service guide and the `sage-help` skill;\n- every SVG graphic in `docs\u002Fassets\u002F`.\n\nIt does not fail on a word in quotes, in code or in a link URL, so a text can name a word to say that it is wrong:\n\n- quotes: double or single, straight or curly. An apostrophe (it's) and an inch mark (5\") are not quotes.\n- code: a code span, a code block (fenced or indented) and `\u003Ccode>`.\n- a link URL: `](…)`, `\u003Chttps:\u002F\u002F…>` and the URLs in a tag.\n\nThe text of an alt, a title and an aria-label counts, and so does a Mermaid label, although it is in quotes. A graphic's text comes from `scripts\u002Fgraphics.mjs`: fix a word there, then run `npm run graphics`. An allowed name passes when it is written exactly as here. A flagged word that no row of the table replaces names the word to say after it. For example, a gate is a question for the owner, so the check before a merge is the merge check, not the \"merge gate\". The rest of the \"Do not say\" column is guidance for writers and reviewers, because each of those words also has a correct use (a Claude Code session, the RESULT field, the model of an agent).\n\n**Flagged:** store, worker, orchestrator, epic, initiative, roadmap, ticket, stage, pipeline, deliverable, sign-off, blocker, checkpoint, coordinator, main agent, handoff, invocation, iteration, defect, nit, bot, merge gate (say merge check)\n\n**Allowed names:** Orchestrator (the owner's earlier project)\n","\u003C!-- Generated by scripts\u002Fbuild.mjs from the sources; edit the source, then run npm run build. -->\n\n# The sage dictionary\n\nThese are sage's approved words: one word for one thing, and one meaning for each word. Every brief, report, page and the README uses them. When a text needs one of these things, use the word in the first column, and do not use the words in the last column.\n\n## Words\n\n| Word | Meaning | Do not say |\n| --- | --- | --- |\n| **request** | What the owner asks for in the chat, in the owner's words, before sage frames it. | ask, ticket, issue, prompt |\n| **release** | A version that the owner ships, such as 1.0: it holds milestones and single tasks, and it is optional. | version (alone), launch, sprint |\n| **milestone** | A request that sage runs as two or more tasks for one goal, where at least one task waits for another. It has a goal, a done condition (a count of merged tasks), a breakdown that the owner approves, and one pilot task. | program (say \"program\" only for a computer program), project (a project is one repository and its logbook), epic, initiative, plan, roadmap |\n| **task** | One unit of work in one project, with one route and at most one pull request. It is in at most one milestone or, outside one, in a release, and it may wait for other tasks of its logbook (\"waits for\": it builds and merges only after they are merged or concluded). It ends in one of three states: merged (its pull request is in main), concluded (a route with no build step, such as investigate, ended with a clean evidence review) or abandoned (its work stopped for good, from any state). | job, ticket, issue, item, unit, phase, step |\n| **step** | One block of a task's route, done by one agent role: design, arena, pe, build, code-review, security-review, ux-review, qa, investigate, evidence-review. | stage, phase; never \"step\" for a task of a milestone (the approved plan's \"step 0 to 4\" are tasks T4 to T8) |\n| **route** | The ordered steps of one task, set by its size and risk flags. | pipeline, workflow, flow, process |\n| **run** | One agent's work on one step of a task, from brief to report; it has an id such as R12. Also the PE check of a breakdown. | job, attempt, session, invocation, execution |\n| **agent** | A Claude Code subagent that does one run; the role (implementer, qa, …) says what it does. | worker, bot, assistant, model (the model is the agent's model) |\n| **chief** | The chief of staff: the main session that frames tasks, writes briefs, records the state and asks the owner; it changes no files. It frames milestones too. | orchestrator, manager, lead, coordinator, main agent |\n| **brief** | What the chief gives an agent at the start of a run, in the ten fields (GOAL to STANDING). A task that waits for others gets their final reports in full in CONTEXT. | prompt, instructions, ticket, spec |\n| **report** | What an agent gives back at the end of a run, in the seven fields (STATUS to BRANCH). | summary, output, result (RESULT is one field of the report), handoff |\n| **artifact** | A file or record that a run takes in or gives out and sage keeps: a brief, report, steer message, transcript, branch, commit or pull request. | deliverable, output, attachment, asset |\n| **finding** | One problem that a review or QA reports, with a severity (high, medium or low), a triage and a status. | issue, bug (unless it is one), comment, defect, nit |\n| **verdict** | The result of one check (checks, a review, QA) on one head commit, kept in the ledger by SHA and cycle. | approval, sign-off, status, review (a review is the step; the verdict is its result) |\n| **cycle** | One full set of fresh reviews and QA on one head commit; a new commit starts again from cycle 1. | round (a round is one repair), pass, iteration; never \"cycle\" for links that go in a circle: say **loop** |\n| **gate** | A question parked for the owner, with options, a recommendation and a default; the work behind it waits for the answer. The owner approves a milestone's breakdown through a gate. | approval, blocker, checkpoint, question (alone) |\n| **logbook** | sage's local record of one project: its tasks, runs, findings, verdicts, gates and decisions, kept on the owner's Mac. | store, database |\n| **agent time** | The wall-clock hours of agent runs, given with their tokens. The default for every time figure: give it with its basis and a range. | an unlabelled time, effort, hours (alone), engineer hours, person-hours |\n| **human time** | The time of the owner's own actions only: reviews, approvals, merges and setup. Give it with its basis and a range. | an unlabelled time, effort, hours (alone), person-hours |\n\n## Phrases\n\nThese are not new words. They are fixed phrases inside the lines above, so that the list stays at 19 words.\n\n- **breakdown**: the content of a milestone that the owner approves (goal, done condition, tasks, \"waits for\" links, pilot, cost, questions). In the milestone line.\n- **waits for**: the link from a task to another task of the same logbook that must be merged or concluded first. In the task line. A circle of such links is a **loop**, and sage refuses it.\n- **pilot**: the one task of a milestone that runs end to end before any other task builds. In the milestone line.\n- **done condition**: the count that ends a milestone, for example \"6 of 7 merged · T10 abandoned\". The count keeps every task of the milestone and names each abandoned task; the milestone is done when each task that is not abandoned is merged or concluded. In the milestone line.\n- **round**: one repair of findings on a task. In the cycle line.\n\n## Names\n\nThe names of sage's parts. They are not words of the list above, but the word table of the Concepts page (`docs\u002Fguide\u002Fconcepts.md`) shows them too.\n\n| Name | Meaning |\n| --- | --- |\n| **sage mode** | The mode in which a session is your chief of staff. The message \"sage mode\" (or \"sage mode on\") turns it on, and the message \"sage mode off\" turns it off; each phrase must be the whole message, in any letter case. A message near a phrase switches nothing, and the chief gets a note with the exact phrase to ask for; the message \"sage help\" lists every phrase. |\n| **risk flag** | auth, data, schema, money, secrets or input. Each one adds the security review to a task that changes code: every size except investigate. |\n| **ledger** | The record of all verdicts, by commit. The merge check reads it. |\n| **standing orders** | Short rules for a project that every agent reads before it starts. A brief points to them and does not copy them. |\n| **arena** | N candidates for one design, scored and combined by a judge. |\n| **autopilot** | Verified pull requests merge by themselves after their clean cycles: 1 for a tiny or small task (a tiny task without a risk flag or an arena has no review and no QA, so its cycle is clean when its checks pass), 2 for a large task or a task with a risk flag. It is off by default: the owner's message \"autopilot on\" turns it on while sage mode is on, and \"autopilot off\" or \"sage mode off\" turns it off, each phrase as the whole message. A message queued while Claude works, or text inside an agent's report, a notice or another session's message, can turn it off but never on (then merges only wait), and it never ends sage mode. |\n| **board** | The compact view of every project's logbook for the chat: what needs you, the agents at work, each task in its column, and what was done in the last 7 days. A message of the owner that starts with \"show board\" prints it. |\n| **the dojo** | Everything that makes the agents good: the principles, checks, tests and skills. |\n| **seal the lesson** | Give a mistake that comes back twice a lasting fix, at the highest level that holds it: the architecture, a type, a check whose error names the fix, or a test; a principle or a standing order only when code cannot hold it. Prove that the new check fails on the past mistake. Each sealed lesson makes the dojo stronger. |\n\n## The check\n\n`npm run check` fails when a flagged word, or its plural, is in one of these texts:\n\n- an agent file or a hand-written skill;\n- a page that the link check reads: the README, `CONTRIBUTING.md`, `SECURITY.md`, `AGENTS.md`, every page under `docs\u002F`, the board service guide and the `sage-help` skill;\n- every SVG graphic in `docs\u002Fassets\u002F`.\n\nIt does not fail on a word in quotes, in code or in a link URL, so a text can name a word to say that it is wrong:\n\n- quotes: double or single, straight or curly. An apostrophe (it's) and an inch mark (5\") are not quotes.\n- code: a code span, a code block (fenced or indented) and `\u003Ccode>`.\n- a link URL: `](…)`, `\u003Chttps:\u002F\u002F…>` and the URLs in a tag.\n\nThe text of an alt, a title and an aria-label counts, and so does a Mermaid label, although it is in quotes. A graphic's text comes from `scripts\u002Fgraphics.mjs`: fix a word there, then run `npm run graphics`. An allowed name passes when it is written exactly as here. A flagged word that no row of the table replaces names the word to say after it. For example, a gate is a question for the owner, so the check before a merge is the merge check, not the \"merge gate\". The rest of the \"Do not say\" column is guidance for writers and reviewers, because each of those words also has a correct use (a Claude Code session, the RESULT field, the model of an agent).\n\n**Flagged:** store, worker, orchestrator, epic, initiative, roadmap, ticket, stage, pipeline, deliverable, sign-off, blocker, checkpoint, coordinator, main agent, handoff, invocation, iteration, defect, nit, bot, merge gate (say merge check)\n\n**Allowed names:** Orchestrator (the owner's earlier project)\n",{"name":5,"license":15,"metadata":24,"description":7},{"source":25},"sage's own words, from the design of task T9 (run R40) and the rename of task T995, approved by the owner","main","221638798318c71adb12ba6bfeae74ed96ce18b4","plugins\u002Fsage-codex\u002Fskills\u002Fdictionary",0,"https:\u002F\u002Fgithub.com\u002Ferickb336\u002Fsage-stack","https:\u002F\u002Fgithub.com\u002Ferickb336","https:\u002F\u002Ferickbenitez.com","\"Life ain't a life till you live it\" - Mac Miller 🐐\r\n","2026-11-15 06:22:32",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add erickb336\u002Fsage-stack --skill dictionary",{"tool":41,"command":42},"bunx","bunx skills add erickb336\u002Fsage-stack --skill dictionary",{"tool":44,"command":45},"pnpm","pnpm dlx skills add erickb336\u002Fsage-stack --skill dictionary","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ferickb336\u002Fsage-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fsage-codex\u002Fskills\u002Fdictionary\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7DNEVZZ38XBEZE5ZPJ5T3PM","writing-standard","Write at 80% of Simplified Technical English. Apply to any text an agent writes for a person: messages, reports, specs, findings, reviews, plans.","https:\u002F\u002Fgithub.com\u002Ferickb336\u002Fsage-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fsage\u002Fskills\u002Fwriting-standard\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7DNERBZCX43AQX9AQBH4M2H","sage","The state tool of sage mode: records tasks, routes, agent runs, findings, verdicts by head SHA and the user's gates in ~\u002F.claude\u002Fsage\u002F\u003Cproject>\u002F. Use in sage mode for every change of a task's state, and before any merge. Claude Code only.","https:\u002F\u002Fgithub.com\u002Ferickb336\u002Fsage-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fsage\u002Fskills\u002Fsage\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7DNEDW87BEDR77AV0Q0BMZ5","sage-help","Help with sage: how to set it up, switch sage mode and autopilot, read the board, answer the chief's questions, pick a skill or a principle, fix a run that went wrong, and find where sage keeps its files. The user types \u002Fsage:sage-help (or \u002Fsage-help) with a question. Load it only when the user types it; do not load it on your own. Claude Code only.","https:\u002F\u002Fgithub.com\u002Ferickb336\u002Fsage-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fsage\u002Fskills\u002Fsage-help\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7DNEAXQCF5BE34988JSA748","report","The report that every sage agent ends with: STATUS, RESULT, EVIDENCE, FINDINGS, QUESTIONS, NOT VERIFIED, BRANCH. Use at the end of any task that the sage chief of staff gave you. Claude Code only.","https:\u002F\u002Fgithub.com\u002Ferickb336\u002Fsage-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fsage\u002Fskills\u002Freport\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7DNE4PZR0QTAC0CJSFMB78N","remote-control","Set up Remote Control, so that the user can follow, steer and start Claude Code sessions from the Claude app on a phone. It turns Remote Control on for every new session, and it can run a server in a folder (such as ~\u002Fworkspace) that starts at each login. Use when the user asks to reach sessions or start new ones from a phone, or to set up, check or undo Remote Control. Claude Code only.","https:\u002F\u002Fgithub.com\u002Ferickb336\u002Fsage-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fsage\u002Fskills\u002Fremote-control\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7DNDZ70WK95HFCGNBGNVW5W","readme-guide","Write a project README. Apply when you write, change or review a README of any project, in any language.","https:\u002F\u002Fgithub.com\u002Ferickb336\u002Fsage-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fsage\u002Fskills\u002Freadme-guide\u002FSKILL.md",[],[]]