[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C4BANX2KC024DCKZ39TCJE":3,"skill-same:01M6C4BANX2KC024DCKZ39TCJE":49},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":21,"linkOnly":22,"markdownContent":23,"markdownBody":24,"frontMatter":25,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":11,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M6C4BANX2KC024DCKZ39TCJE","cast-org",null,"codecast-sh\u002Fcodecast","codecast-sh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F248798196?v=4","01M6C4A0X9D10K5VATDQRDCE36","codecast.sh","01M6C4A11M3RRJVEJQDCSZZTNR",49,"MIT","https:\u002F\u002Fgithub.com\u002Fcodecast-sh\u002Fcodecast\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fskills\u002Fcast-org\u002FSKILL.md",[],[18,19,20],"cast org","cast","org","2026-11-10 10:12:30",false,"---\nname: cast-org\ndescription: Talk through the organization of agents and people around this work with the person, in this session: who reports to whom, what each role looks after, where their sessions go. Reads what the code and the sessions say before it trusts a plan or a task, asks what the records cannot settle, and posts each agreed change as a small proposal that renders inline for them to approve. Use when asked who is working on what, to set up or review the org, to hire a lead or a head of people, or when the chart has drifted from reality.\nargument-hint: \"[--team \u003Cname>|personal] [what to change, in plain words]\"\n---\n\nThe organization is read from the top down: initiatives, the goals the\ncompany set; the projects that carry each; the plans and tasks inside a\nproject; the roles that lead projects and own initiatives; the people they\nreport to; and the sessions that do the work. This skill is the conversation\nabout it, held where the person already is. The org page holds the same\nconversation beside the chart. A change is approved on a card here or on that\npage, and nothing moves until they approve it.\n\n## Look first\n\nEvery org verb reads the active workspace unless `--team` names another;\n`--team personal` is the person's own. Say which workspace you are looking\nat in your first line: the wrong company is the commonest wrong answer\nhere, and a list of roles does not reveal it.\n\n```bash\ncast org ls                      # people, roles with their scopes, the sessions under each\ncast org proposals               # anything already waiting on a person\ncast org health                  # load, flags, stale records, span\ncast initiative ls               # the goals: status, owner, health, target\ncast org inputs                  # ends with coverage: projects with a lead, work outside any project\n```\n\nThen:\n\n```bash\ncast org init --here             # no roles yet: the briefing, in this session\ncast org review --here           # roles exist: the same briefing in review mode\n```\n\nFollow the briefing it prints. It carries what to read, the grounding rules,\nthe initiative and coverage rules, the capacity model, the standing versus\nprogram rule, the honesty rules, the spec, and how the conversation is held;\ndo not restate or replace them.\n\nWhen one person works in one area with nothing filed, there is nothing to\norganize: say so, say what would make a chart worth having, and stop.\n\n## The conversation\n\nRead everything first, then talk. Lead with the reporting structure: who\nreports to whom, what each role looks after, and where the person's own\nsessions go, as it stands and as you would change it. Short messages in\nplain words, one thing at a time. Ask what the records cannot settle, take\nthe answer, and move on. Hold the evidence and give it when asked; no ids in\nprose, nothing about yourself.\n\nWhen something is agreed, or the records settle it on their own, post it as\na small proposal:\n\n```bash\ncast org propose --spec proposal.json [--supersedes op-N]\n```\n\nPut its short id on its own line, where it renders as a card. The card says\neach change in a plain sentence, with what was there before and the reason\nyou gave. The command also prints each change's number. When the conversation\nturns to one change, write the short id, `#` and that number on its own\nline, and it renders as the card for the one role, goal or record it changes.\n\nThe person answers the card: they approve a change, reject it or write back\non it, and their answers reach you together, as one message that names each\nchange. What they approved is already applied when you read it. Their words\non a rejection or a note are their edit: revise the proposal from them and\nsay what changed in a sentence.\n\nMany small proposals over the conversation, never one document. An edit the\nperson gives in plain words folds into the next proposal, or into one you\nposted, in place:\n\n```bash\ncast org revise op-N --remove 3 --note \"growth is not dead yet\"\ncast org revise op-N --amend 1 --edits '{\"scope\":{\"add\":[\"pr-12\"]}}' --rationale \"why\"\ncast org revise op-N --add change.json          # one spec change, or a list\n```\n\nA change they already decided is refused by name, a rejected one included:\nwhat replaces it goes in with `--add`. A change they wrote back on still\nwaits, and takes `--amend`. A proposal somebody else posted is theirs: an\nedit on it lands on the page by change number, and a withdraw is theirs, on\nthe page or with `cast org proposals --withdraw op-N` at their own shell.\n\nProposals already open outrank a new one on the same subject. Read them\nback in a few plain lines, compare with what health says now, and name a\ndifference only where it would move a change. Do not post their changes\nagain and do not withdraw them.\n\n## End\n\nA change no proposal carries, a role retired, created or moved by hand, is\nmade on the org page and nowhere else; a shell is refused, so point them at\nthe page, not at a command. The hire and every approval are theirs: no session\ndecides a staffing change. A head of people, once hired (`cast org staff`, or\nthe button on the page), holds this conversation weekly without them.\n","The organization is read from the top down: initiatives, the goals the\ncompany set; the projects that carry each; the plans and tasks inside a\nproject; the roles that lead projects and own initiatives; the people they\nreport to; and the sessions that do the work. This skill is the conversation\nabout it, held where the person already is. The org page holds the same\nconversation beside the chart. A change is approved on a card here or on that\npage, and nothing moves until they approve it.\n\n## Look first\n\nEvery org verb reads the active workspace unless `--team` names another;\n`--team personal` is the person's own. Say which workspace you are looking\nat in your first line: the wrong company is the commonest wrong answer\nhere, and a list of roles does not reveal it.\n\n```bash\ncast org ls                      # people, roles with their scopes, the sessions under each\ncast org proposals               # anything already waiting on a person\ncast org health                  # load, flags, stale records, span\ncast initiative ls               # the goals: status, owner, health, target\ncast org inputs                  # ends with coverage: projects with a lead, work outside any project\n```\n\nThen:\n\n```bash\ncast org init --here             # no roles yet: the briefing, in this session\ncast org review --here           # roles exist: the same briefing in review mode\n```\n\nFollow the briefing it prints. It carries what to read, the grounding rules,\nthe initiative and coverage rules, the capacity model, the standing versus\nprogram rule, the honesty rules, the spec, and how the conversation is held;\ndo not restate or replace them.\n\nWhen one person works in one area with nothing filed, there is nothing to\norganize: say so, say what would make a chart worth having, and stop.\n\n## The conversation\n\nRead everything first, then talk. Lead with the reporting structure: who\nreports to whom, what each role looks after, and where the person's own\nsessions go, as it stands and as you would change it. Short messages in\nplain words, one thing at a time. Ask what the records cannot settle, take\nthe answer, and move on. Hold the evidence and give it when asked; no ids in\nprose, nothing about yourself.\n\nWhen something is agreed, or the records settle it on their own, post it as\na small proposal:\n\n```bash\ncast org propose --spec proposal.json [--supersedes op-N]\n```\n\nPut its short id on its own line, where it renders as a card. The card says\neach change in a plain sentence, with what was there before and the reason\nyou gave. The command also prints each change's number. When the conversation\nturns to one change, write the short id, `#` and that number on its own\nline, and it renders as the card for the one role, goal or record it changes.\n\nThe person answers the card: they approve a change, reject it or write back\non it, and their answers reach you together, as one message that names each\nchange. What they approved is already applied when you read it. Their words\non a rejection or a note are their edit: revise the proposal from them and\nsay what changed in a sentence.\n\nMany small proposals over the conversation, never one document. An edit the\nperson gives in plain words folds into the next proposal, or into one you\nposted, in place:\n\n```bash\ncast org revise op-N --remove 3 --note \"growth is not dead yet\"\ncast org revise op-N --amend 1 --edits '{\"scope\":{\"add\":[\"pr-12\"]}}' --rationale \"why\"\ncast org revise op-N --add change.json          # one spec change, or a list\n```\n\nA change they already decided is refused by name, a rejected one included:\nwhat replaces it goes in with `--add`. A change they wrote back on still\nwaits, and takes `--amend`. A proposal somebody else posted is theirs: an\nedit on it lands on the page by change number, and a withdraw is theirs, on\nthe page or with `cast org proposals --withdraw op-N` at their own shell.\n\nProposals already open outrank a new one on the same subject. Read them\nback in a few plain lines, compare with what health says now, and name a\ndifference only where it would move a change. Do not post their changes\nagain and do not withdraw them.\n\n## End\n\nA change no proposal carries, a role retired, created or moved by hand, is\nmade on the org page and nowhere else; a shell is refused, so point them at\nthe page, not at a command. The hire and every approval are theirs: no session\ndecides a staffing change. A head of people, once hired (`cast org staff`, or\nthe button on the page), holds this conversation weekly without them.\n",{},"main","4f2367cc51fa8b9b25afe4ec8ce91c2dd39208ae","packages\u002Fcli\u002Fskills\u002Fcast-org",6,"https:\u002F\u002Fgithub.com\u002Fcodecast-sh\u002Fcodecast","https:\u002F\u002Fcodecast.sh","https:\u002F\u002Fgithub.com\u002Fcodecast-sh","Making software a team sport","2026-11-15 03:29:42",{"source":7,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add codecast-sh\u002Fcodecast --skill cast-org",{"tool":41,"command":42},"bunx","bunx skills add codecast-sh\u002Fcodecast --skill cast-org",{"tool":44,"command":45},"pnpm","pnpm dlx skills add codecast-sh\u002Fcodecast --skill cast-org","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcodecast-sh\u002Fcodecast\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fskills\u002Fcast-org\u002FSKILL.md",true,[],[50,63,81,106,113,120],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":21},"01M6C4DCX5TKER170ESW6C64V2","something-else-entirely","A skill whose frontmatter name disagrees with its directory name.","https:\u002F\u002Fgithub.com\u002Fcodecast-sh\u002Fcodecast\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fsrc\u002Fcapabilities\u002F__fixtures__\u002Fmanifests\u002Fskills\u002Fwrong-name\u002FSKILL.md",[],[57,58,59,60,61,62],"something else","something else entirely","directory","name","with","frontmatter",{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":74,"publishedAt":21},"01M6C4DAFDKVVPTBS94VNW32S1","unknown-field","Carries a field that is in neither the spec's six nor Claude Code's list.","https:\u002F\u002Fgithub.com\u002Fcodecast-sh\u002Fcodecast\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fsrc\u002Fcapabilities\u002F__fixtures__\u002Fmanifests\u002Fskills\u002Funknown-field\u002FSKILL.md",[69],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[75,76,77,78,79,80],"unknown","unknown field","spec","code","list","neither",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":95,"publishedAt":21},"01M6C4D7N185HPGR0YPVKVX4KY","remotion-best-practices","Best practices for Remotion - Video creation in React","https:\u002F\u002Fgithub.com\u002Fcodecast-sh\u002Fcodecast\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fsrc\u002Fcapabilities\u002F__fixtures__\u002Fmanifests\u002Fskills\u002Fremotion-best-practices\u002FSKILL.md",[87,92],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":93,"categoryName":94,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000016","图像与多媒体",[96,97,98,99,100,101,102,103,104,105],"best practices","remotion best practices","Remotion","react","Video","Animation","Composition","remotion, video, react, animation, composition","creation","for",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":21},"01M6C4D530ZPR6CBNSJ4GE4M3Z","overlength","xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","https:\u002F\u002Fgithub.com\u002Fcodecast-sh\u002Fcodecast\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fsrc\u002Fcapabilities\u002F__fixtures__\u002Fmanifests\u002Fskills\u002Foverlength\u002FSKILL.md",[],[108],{"skillNo":114,"name":115,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":21},"01M6C4D2TM5QDSPN2JWR50WDNJ","no-frontmatter","https:\u002F\u002Fgithub.com\u002Fcodecast-sh\u002Fcodecast\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fsrc\u002Fcapabilities\u002F__fixtures__\u002Fmanifests\u002Fskills\u002Fno-frontmatter\u002FSKILL.md",[],[119,62],"no frontmatter",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":133,"publishedAt":21},"01M6C4CZQCGATTA7K5SA6D18MD","improve","Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models\u002Fagents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.","https:\u002F\u002Fgithub.com\u002Fcodecast-sh\u002Fcodecast\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fsrc\u002Fcapabilities\u002F__fixtures__\u002Fmanifests\u002Fskills\u002Fimprove\u002FSKILL.md",[126,129,130],{"categoryNo":127,"categoryName":128,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},{"categoryNo":131,"categoryName":132,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000031","产品经理",[122,134,135,136,137,138,78,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159],"when","use","implement","test","generate","product","produce","audit","find","read","coverage","execute","tech debt","senior","survey","never","only","roadmap","test coverage","advisor","next","self","project next","project","direction","performance"]