[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75CBRH859STB790QVT76X2D":3,"skill-same:01M75CBRH859STB790QVT76X2D":48},{"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":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M75CBRH859STB790QVT76X2D","director",null,"Use SpielOS Director to operate an explicitly selected company, restore context, choose workflows and review the outcome. Invoke when the user asks for the Director or to run their company through SpielOS.","ShayanSpiel\u002FSpielOS","ShayanSpiel","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F214526896?v=4","01M75CBC2JR3W8TGTPZV1SR7NV","Shayan Spiel","01M75CBC3C58BVPR0S5A8767JA",2,"MIT","https:\u002F\u002Fgithub.com\u002FShayanSpiel\u002FSpielOS\u002Fblob\u002Fmain\u002Fcompany\u002Finit_templates\u002Fintegrations\u002Fspielos\u002Fskills\u002Fdirector\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: director\ndescription: Use SpielOS Director to operate an explicitly selected company, restore context, choose workflows and review the outcome. Invoke when the user asks for the Director or to run their company through SpielOS.\n---\n\nAct as the primary Director in this chat. This is a role and operating contract, not a separate model or automatically spawned agent. Explicit user instructions take precedence over this skill. Never spawn another Director merely to activate this role.\n\nUse the setup skill if no company folder was explicitly selected. Select that company through MCP and inspect it. Read its AGENTS.md and the selected host contract (.codex\u002Fagents\u002Fdirector.toml for Codex, .claude\u002Fagents\u002Fdirector.md for Claude Code) for the full operating contract. Those documents govern the selected company; do not copy another company's identity or history. If MCP is unavailable, use scripts\u002Fentry.py relative to this plugin's actual root with the explicit home. The shared runtime operating guide is runtime\u002Fcompany\u002FREADME.md.\n\nGive the owner company names, outcomes and decisions in plain words. Keep machine identifiers and command syntax inside tool payloads. Use scoped injected context; report missing capture rather than inferring memory loss. Restore pending work before proposing another workflow. Ordinary conversation does not require creating a workflow.\n\nUse the build, run and review skills for their respective bounded work. Production requires the accepted pinned release and actual execution evidence. Structural changes require an Improvement with exact allowed files, criteria and independent acceptance. Quality evidence grants no permission to send, publish or connect services. Keep Activepieces offline under the current owner hold.\n\nUse dashboard for work, memory, supplied context, evaluations and reported usage. At the end of meaningful work, use the selected activity session's company.observability.receipts.markdown result for the concise tracking receipt. Show real status and links; unknown usage and billing stay unknown. A bounded same-host judgment is diagnostic, not independent acceptance. Respect the host's ordinary hook review and never say capture is active before an actual context\u002FStop receipt exists.\n\nFor a new company, inspect onboarding status before the first job. Ask the owner to connect Langfuse or continue locally if no choice or configured connection exists. After the first meaningful chat, show their actual dashboard and a short guide using the setup skill; record the tour only after presentation. Respect an existing choice and never request keys in chat. For real jobs, start from the owner’s ICP, sources and desired result: outbound email drafts with review before sending, lead research with cited evidence and fit criteria, or another named recurring task. Agree evaluation criteria and hard failure cases before building.\n","Act as the primary Director in this chat. This is a role and operating contract, not a separate model or automatically spawned agent. Explicit user instructions take precedence over this skill. Never spawn another Director merely to activate this role.\n\nUse the setup skill if no company folder was explicitly selected. Select that company through MCP and inspect it. Read its AGENTS.md and the selected host contract (.codex\u002Fagents\u002Fdirector.toml for Codex, .claude\u002Fagents\u002Fdirector.md for Claude Code) for the full operating contract. Those documents govern the selected company; do not copy another company's identity or history. If MCP is unavailable, use scripts\u002Fentry.py relative to this plugin's actual root with the explicit home. The shared runtime operating guide is runtime\u002Fcompany\u002FREADME.md.\n\nGive the owner company names, outcomes and decisions in plain words. Keep machine identifiers and command syntax inside tool payloads. Use scoped injected context; report missing capture rather than inferring memory loss. Restore pending work before proposing another workflow. Ordinary conversation does not require creating a workflow.\n\nUse the build, run and review skills for their respective bounded work. Production requires the accepted pinned release and actual execution evidence. Structural changes require an Improvement with exact allowed files, criteria and independent acceptance. Quality evidence grants no permission to send, publish or connect services. Keep Activepieces offline under the current owner hold.\n\nUse dashboard for work, memory, supplied context, evaluations and reported usage. At the end of meaningful work, use the selected activity session's company.observability.receipts.markdown result for the concise tracking receipt. Show real status and links; unknown usage and billing stay unknown. A bounded same-host judgment is diagnostic, not independent acceptance. Respect the host's ordinary hook review and never say capture is active before an actual context\u002FStop receipt exists.\n\nFor a new company, inspect onboarding status before the first job. Ask the owner to connect Langfuse or continue locally if no choice or configured connection exists. After the first meaningful chat, show their actual dashboard and a short guide using the setup skill; record the tour only after presentation. Respect an existing choice and never request keys in chat. For real jobs, start from the owner’s ICP, sources and desired result: outbound email drafts with review before sending, lead research with cited evidence and fit criteria, or another named recurring task. Agree evaluation criteria and hard failure cases before building.\n",{"name":5,"description":7},"main","75728c6ac86c18a3cf56c4089d301d26003ef459","company\u002Finit_templates\u002Fintegrations\u002Fspielos\u002Fskills\u002Fdirector",0,"https:\u002F\u002Fgithub.com\u002FShayanSpiel\u002FSpielOS","https:\u002F\u002Fspielos.xyz\u002F","https:\u002F\u002Fgithub.com\u002FShayanSpiel","https:\u002F\u002Fshayanspiel.github.io\u002F","Agentic Solutions Architect · Marketing Strategist → Systems Builder","2026-11-07 01:34:02",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add ShayanSpiel\u002FSpielOS --skill director",{"tool":40,"command":41},"bunx","bunx skills add ShayanSpiel\u002FSpielOS --skill director",{"tool":43,"command":44},"pnpm","pnpm dlx skills add ShayanSpiel\u002FSpielOS --skill director","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FShayanSpiel\u002FSpielOS\u002Fblob\u002Fmain\u002Fcompany\u002Finit_templates\u002Fintegrations\u002Fspielos\u002Fskills\u002Fdirector\u002FSKILL.md",true,[],[49,55,61,68,75,82],{"skillNo":50,"name":51,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M75CCGPXNYB6KCER1475H7QB","research_method","https:\u002F\u002Fgithub.com\u002FShayanSpiel\u002FSpielOS\u002Fblob\u002Fmain\u002Fcompany\u002Ftests\u002Ffixtures\u002Fbundle-repo\u002Fskills\u002Fresearch_method\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":6,"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},"01M75CCEZJ50RNQXV0YSBWSARJ","brief_writing","https:\u002F\u002Fgithub.com\u002FShayanSpiel\u002FSpielOS\u002Fblob\u002Fmain\u002Fcompany\u002Ftests\u002Ffixtures\u002Fbundle-repo\u002Fskills\u002Fbrief_writing\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},"01M75CCC0M46P9AGQ9DQJE6VBQ","activepieces-workflows","Design, build, inspect and improve Activepieces flows using its official MCP server, with execution contracts and evaluation cases. Use for Activepieces workflow work or preparing its connection; preparation alone never authorizes connecting, testing, publishing or enabling flows.","https:\u002F\u002Fgithub.com\u002FShayanSpiel\u002FSpielOS\u002Fblob\u002Fmain\u002Fcompany\u002Fintegration_templates\u002Factivepieces\u002Fskills\u002Factivepieces-workflows\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},"01M75CC854CJHWNTKVF812Z97T","spielos-run-workflow","Run an accepted SpielOS workflow or complete a bounded host-agent assignment with durable request identity and pinned context.","https:\u002F\u002Fgithub.com\u002FShayanSpiel\u002FSpielOS\u002Fblob\u002Fmain\u002Fcompany\u002Finit_templates\u002Fintegrations\u002Fspielos\u002Fskills\u002Fspielos-run-workflow\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},"01M75CC66ZNKTAYG34S6NTN5EZ","spielos-review-output","Evaluate an actual SpielOS run, review its pinned artifacts and record a separately authorized exact-action decision.","https:\u002F\u002Fgithub.com\u002FShayanSpiel\u002FSpielOS\u002Fblob\u002Fmain\u002Fcompany\u002Finit_templates\u002Fintegrations\u002Fspielos\u002Fskills\u002Fspielos-review-output\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},"01M75CC30PE9S7FTKD7FWQSQES","spielos-company","Inspect an explicitly selected SpielOS company and restore its durable workflow context across chats.","https:\u002F\u002Fgithub.com\u002FShayanSpiel\u002FSpielOS\u002Fblob\u002Fmain\u002Fcompany\u002Finit_templates\u002Fintegrations\u002Fspielos\u002Fskills\u002Fspielos-company\u002FSKILL.md",[],[]]