[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71P4DCSGE0PNGGP3B98ZSBH":3,"skill-same:01M71P4DCSGE0PNGGP3B98ZSBH":68},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":45,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M71P4DCSGE0PNGGP3B98ZSBH","studio-operations",null,"Use when an org role acts as studio operations lead and must keep a creative or game studio's tools, pipelines, budgets and vendor logistics running. Covers pipeline friction as backlog, milestone-tied budget burn, standardized processes and contractor terms. For scope and schedule see studio-producer.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fstudio-operations\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"operations","studio operations","studio","running","Tools","lead","org","logistics","Budget","game-dev","monomind","leadership","game","milestone","schedule","game studio","when","pipeline","scope","producer","2026-11-10 10:56:23",false,"---\nname: studio-operations\ndescription: \"Use when an org role acts as studio operations lead and must keep a creative or game studio's tools, pipelines, budgets and vendor logistics running. Covers pipeline friction as backlog, milestone-tied budget burn, standardized processes and contractor terms. For scope and schedule see studio-producer.\"\ntags: [\"leadership\",\"operations\",\"game-dev\"]\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\n---\n# Studio Operations — Best Practices\n\n## Focus\nKeeps the studio's operating infrastructure running — tools, pipelines, budgets, vendor\u002Fcontractor logistics, and the processes that let creative teams focus on making the thing instead of fighting the environment.\n\n## Best practices\n- Treat tooling and pipeline friction as a first-class backlog item, not an afterthought — time lost to broken build pipelines or asset tools compounds across the whole team.\n- Keep budget burn visible and tied to milestones, not just calendar months — a team can be \"on budget\" monthly while badly overspent against remaining scope.\n- Standardize repeatable processes (onboarding, asset submission, build cadence) so they don't depend on one person's memory.\n- Negotiate vendor\u002Fcontractor terms with clear deliverables and kill criteria before work starts, not after it's late.\n- Audit access and licenses periodically — unused seats and stale permissions are both cost and risk.\n- Build in slack for the unglamorous work (tooling upkeep, license renewals, backup verification) — it never wins a prioritization fight on its own.\n- Make the studio's operating rhythm (standups, reviews, builds) predictable enough that people can plan around it.\n\n## Common pitfalls\n- Letting pipeline\u002Ftooling debt accumulate because it's invisible until it causes a production-blocking failure.\n- Tracking budget against total allocation instead of against burn rate relative to remaining milestones.\n- Onboarding new contractors\u002Fhires ad hoc each time instead of maintaining a repeatable checklist.\n- Treating operations as purely reactive (firefighting) instead of building preventive process.\n\n## Tools & techniques\n- Burn-rate dashboards tied to milestone completion, not just calendar spend.\n- Standardized onboarding\u002Foffboarding checklists for contractors, vendors, and new hires.\n- Pipeline health checks (build times, asset submission failures) tracked over time like any other metric.\n- Vendor scorecards — deliverable quality, timeliness, cost — reviewed before renewal decisions.\n","# Studio Operations — Best Practices\n\n## Focus\nKeeps the studio's operating infrastructure running — tools, pipelines, budgets, vendor\u002Fcontractor logistics, and the processes that let creative teams focus on making the thing instead of fighting the environment.\n\n## Best practices\n- Treat tooling and pipeline friction as a first-class backlog item, not an afterthought — time lost to broken build pipelines or asset tools compounds across the whole team.\n- Keep budget burn visible and tied to milestones, not just calendar months — a team can be \"on budget\" monthly while badly overspent against remaining scope.\n- Standardize repeatable processes (onboarding, asset submission, build cadence) so they don't depend on one person's memory.\n- Negotiate vendor\u002Fcontractor terms with clear deliverables and kill criteria before work starts, not after it's late.\n- Audit access and licenses periodically — unused seats and stale permissions are both cost and risk.\n- Build in slack for the unglamorous work (tooling upkeep, license renewals, backup verification) — it never wins a prioritization fight on its own.\n- Make the studio's operating rhythm (standups, reviews, builds) predictable enough that people can plan around it.\n\n## Common pitfalls\n- Letting pipeline\u002Ftooling debt accumulate because it's invisible until it causes a production-blocking failure.\n- Tracking budget against total allocation instead of against burn rate relative to remaining milestones.\n- Onboarding new contractors\u002Fhires ad hoc each time instead of maintaining a repeatable checklist.\n- Treating operations as purely reactive (firefighting) instead of building preventive process.\n\n## Tools & techniques\n- Burn-rate dashboards tied to milestone completion, not just calendar spend.\n- Standardized onboarding\u002Foffboarding checklists for contractors, vendors, and new hires.\n- Pipeline health checks (build times, asset submission failures) tracked over time like any other metric.\n- Vendor scorecards — deliverable quality, timeliness, cost — reviewed before renewal decisions.\n",{"name":5,"tags":43,"tools":44,"source":45,"license":14,"description":7},[29,18,27],[],"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fstudio-operations",2,"https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-14 03:30:52",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add monoes\u002Fmonomind --skill studio-operations",{"tool":60,"command":61},"bunx","bunx skills add monoes\u002Fmonomind --skill studio-operations",{"tool":63,"command":64},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill studio-operations","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fstudio-operations\u002FSKILL.md",true,[],[69,79,87,95,103,111],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":73,"licenseFileUrl":74,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":78},"01M73YHAZDWV4ZVTGSKMWQ4Z1S","isms-audit-expert","Use when planning or running an ISO 27001 ISMS audit: risk-based audit schedules, Annex A control assessment, Statement of Applicability and nonconformities. Auditor-side procedures, versus compliance-auditor, which is org role guidance across SOC 2, HIPAA and PCI-DSS.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fisms-audit-expert\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fisms-audit-expert\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":78},"01M73YGBS2APTY71Y4CYA2DKSQ","instrument-data-to-allotrope","Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full ASM JSON, flattened CSV for easy import, and exportable Python code for data engineers. Common triggers include converting instrument files, standardizing lab data, preparing data for upload to LIMS\u002FELN systems, or generating parser code for production pipelines.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Finstrument-data-to-allotrope\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Finstrument-data-to-allotrope\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":73,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":78},"01M73YB23X4NP40R73TS6YY8TX","experiment-designer","Use when planning a product A\u002FB or multivariate test: If\u002FThen\u002FBecause hypotheses, primary and guardrail metrics, sample size and MDE, ICE prioritization. For logging and reproducing ML runs use experiment-tracker; for scientific study design use experimental-design.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fexperiment-designer\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fexperiment-designer\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":78},"01M73Y8ETSB9072G5ZGPPR0X6E","digest","Generate a daily or weekly digest of activity across all connected sources. Use when catching up after time away, starting the day and wanting a summary of mentions and action items, or reviewing a week's decisions and document updates grouped by project.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fdigest\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fdigest\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":78},"01M73Y7XJJBH0QXCM5GKJW6N21","design-critique","Get structured design feedback on usability, hierarchy, and consistency. Trigger with \"review this design\", \"critique this mockup\", \"what do you think of this screen?\", or when sharing a Figma link or screenshot for feedback at any stage from exploration to final polish.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fdesign-critique\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fdesign-critique\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":73,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":78},"01M73Y7SM786ZEMNXGPT595AM3","deployment-pipeline-design","Use when architecting a multi-stage CI\u002FCD pipeline with approval gates, SAST and DAST scans, environment promotion, canary rollout and automated rollback. Design-level; for concrete Dockerfile and health check patterns use deployment-patterns.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fdeployment-pipeline-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fdeployment-pipeline-design\u002FSKILL.md",[],[]]