[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75CCC0M46P9AGQ9DQJE6VBQ":3,"skill-same:01M75CCC0M46P9AGQ9DQJE6VBQ":58},{"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},"01M75CCC0M46P9AGQ9DQJE6VBQ","activepieces-workflows",null,"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.","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\u002Fintegration_templates\u002Factivepieces\u002Fskills\u002Factivepieces-workflows\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: activepieces-workflows\ndescription: 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.\n---\n\nUse Activepieces' built-in project MCP server. Do not create a competing wrapper or guess action names, properties, connections, sample data or successful runs. Distinguish preparing a connection, creating a draft, testing it and enabling live execution.\n\nIf the owner says to prepare but not use Activepieces, work offline: maintain this skill, connection template and acceptance brief. Do not open OAuth, enable the server, discover live tools, create flows, run tests or publish. A later explicit instruction to use Activepieces lifts that temporary hold for its named task; it is not a permanent product restriction.\n\nFor connection preparation read [connection.md](references\u002Fconnection.md). For actual workflow work read [building.md](references\u002Fbuilding.md), then discover current tool names and schemas in the connected client. The documented catalog is a guide, not evidence that a selected deployment exposes those tools.\n\nUse bounded GODAE:\n\n- Goal: agree the useful output, accountable owner, business outcome window, baseline or explicit unknown, permissions and spending bounds.\n- Observe: inspect the actual process and existing flow before changes. Collect representative inputs, a good reference output, held-out cases and unacceptable outputs. Keep artifact quality separate from downstream business impact.\n- Decide: select a simple provider-native graph and design execution plus evaluation around the same stable criterion identities. Explain data mappings, side effects, timeout, retry\u002Freplay handling, costs and recovery.\n- Act: build a disabled draft within the authorized scope. Validate structure and configuration before any authorized tests. Inspect real outputs; rendered media needs visual inspection. An API success or green run status alone does not establish quality.\n- Evaluate: compare each case\u002Fcriterion with its reference and rating anchors; retain explanations and artifact digests. Empty\u002Fduplicate\u002Fmissing coverage fails release. Record accept, revise or reject with the actual reviewer and exact flow version.\n\nReview the acceptance brief and architecture, then the candidate release; add intermediate owner interruptions only for a real decision, permission boundary or explicit policy. Do not infer causal strategy from a flat metric or promote repeated work automatically.\n\nKeep provider execution and SpielOS evaluation records linked by flow\u002Fversion\u002Frun identities and stable request identity. The remote platform owns its internal graph and scheduling. A published provider version is different from a reviewed SpielOS release; a completed run is different from an accepted output. Record measured, estimated or unknown usage\u002Fcost, including evaluator and retry cost. Never invent tokens or costs.\n\nDraft creation is not publication approval. Publishing, enabling, scheduling, sending or rerunning a flow with effects requires authorization for the exact version, action, destination, content and scope. A test can send real messages or incur charges. Check the selected test's effects before running it. After an ambiguous response inspect flow\u002Frun state; never blindly repeat creation, publishing or an external action. Do not automatically switch providers or broaden permissions when a tool is missing.\n","Use Activepieces' built-in project MCP server. Do not create a competing wrapper or guess action names, properties, connections, sample data or successful runs. Distinguish preparing a connection, creating a draft, testing it and enabling live execution.\n\nIf the owner says to prepare but not use Activepieces, work offline: maintain this skill, connection template and acceptance brief. Do not open OAuth, enable the server, discover live tools, create flows, run tests or publish. A later explicit instruction to use Activepieces lifts that temporary hold for its named task; it is not a permanent product restriction.\n\nFor connection preparation read [connection.md](references\u002Fconnection.md). For actual workflow work read [building.md](references\u002Fbuilding.md), then discover current tool names and schemas in the connected client. The documented catalog is a guide, not evidence that a selected deployment exposes those tools.\n\nUse bounded GODAE:\n\n- Goal: agree the useful output, accountable owner, business outcome window, baseline or explicit unknown, permissions and spending bounds.\n- Observe: inspect the actual process and existing flow before changes. Collect representative inputs, a good reference output, held-out cases and unacceptable outputs. Keep artifact quality separate from downstream business impact.\n- Decide: select a simple provider-native graph and design execution plus evaluation around the same stable criterion identities. Explain data mappings, side effects, timeout, retry\u002Freplay handling, costs and recovery.\n- Act: build a disabled draft within the authorized scope. Validate structure and configuration before any authorized tests. Inspect real outputs; rendered media needs visual inspection. An API success or green run status alone does not establish quality.\n- Evaluate: compare each case\u002Fcriterion with its reference and rating anchors; retain explanations and artifact digests. Empty\u002Fduplicate\u002Fmissing coverage fails release. Record accept, revise or reject with the actual reviewer and exact flow version.\n\nReview the acceptance brief and architecture, then the candidate release; add intermediate owner interruptions only for a real decision, permission boundary or explicit policy. Do not infer causal strategy from a flat metric or promote repeated work automatically.\n\nKeep provider execution and SpielOS evaluation records linked by flow\u002Fversion\u002Frun identities and stable request identity. The remote platform owns its internal graph and scheduling. A published provider version is different from a reviewed SpielOS release; a completed run is different from an accepted output. Record measured, estimated or unknown usage\u002Fcost, including evaluator and retry cost. Never invent tokens or costs.\n\nDraft creation is not publication approval. Publishing, enabling, scheduling, sending or rerunning a flow with effects requires authorization for the exact version, action, destination, content and scope. A test can send real messages or incur charges. Check the selected test's effects before running it. After an ambiguous response inspect flow\u002Frun state; never blindly repeat creation, publishing or an external action. Do not automatically switch providers or broaden permissions when a tool is missing.\n",{"name":5,"description":7},"main","75728c6ac86c18a3cf56c4089d301d26003ef459","company\u002Fintegration_templates\u002Factivepieces\u002Fskills\u002Factivepieces-workflows",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 activepieces-workflows",{"tool":40,"command":41},"bunx","bunx skills add ShayanSpiel\u002FSpielOS --skill activepieces-workflows",{"tool":43,"command":44},"pnpm","pnpm dlx skills add ShayanSpiel\u002FSpielOS --skill activepieces-workflows","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FShayanSpiel\u002FSpielOS\u002Fblob\u002Fmain\u002Fcompany\u002Fintegration_templates\u002Factivepieces\u002Fskills\u002Factivepieces-workflows\u002FSKILL.md",true,[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fbuilding.md","REFERENCE","参考文档",3225,"https:\u002F\u002Fgithub.com\u002FShayanSpiel\u002FSpielOS\u002Fblob\u002Fmain\u002Fcompany\u002Fintegration_templates\u002Factivepieces\u002Fskills\u002Factivepieces-workflows\u002Freferences\u002Fbuilding.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fconnection.md",1775,"https:\u002F\u002Fgithub.com\u002FShayanSpiel\u002FSpielOS\u002Fblob\u002Fmain\u002Fcompany\u002Fintegration_templates\u002Factivepieces\u002Fskills\u002Factivepieces-workflows\u002Freferences\u002Fconnection.md",[59,65,71,78,85,92],{"skillNo":60,"name":61,"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":62,"categories":63,"keywords":64,"publishedAt":19},"01M75CCGPXNYB6KCER1475H7QB","research_method","https:\u002F\u002Fgithub.com\u002FShayanSpiel\u002FSpielOS\u002Fblob\u002Fmain\u002Fcompany\u002Ftests\u002Ffixtures\u002Fbundle-repo\u002Fskills\u002Fresearch_method\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"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":68,"categories":69,"keywords":70,"publishedAt":19},"01M75CCEZJ50RNQXV0YSBWSARJ","brief_writing","https:\u002F\u002Fgithub.com\u002FShayanSpiel\u002FSpielOS\u002Fblob\u002Fmain\u002Fcompany\u002Ftests\u002Ffixtures\u002Fbundle-repo\u002Fskills\u002Fbrief_writing\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},"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":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},"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":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},"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",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M75CBZXWCBNGBG3H4R6WXD4D","spielos-build-workflow","Create or improve a reusable SpielOS workflow through a bounded GODAE record and actual candidate execution evidence.","https:\u002F\u002Fgithub.com\u002FShayanSpiel\u002FSpielOS\u002Fblob\u002Fmain\u002Fcompany\u002Finit_templates\u002Fintegrations\u002Fspielos\u002Fskills\u002Fspielos-build-workflow\u002FSKILL.md",[],[]]