[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EB4B8RKNFC8ZDAQT8GQYP8":3,"skill-same:01M7EB4B8RKNFC8ZDAQT8GQYP8":70},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7EB4B8RKNFC8ZDAQT8GQYP8","calle-script-advisor",null,"Draft and check CALL-E phone-call task text and result schemas for clarity, safety, and extraction quality before any call is placed.","fozagtx\u002FBuildOS-workflow","fozagtx","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160292135?v=4","01M7EAS4W39D2X3WNCCVVZ7CVZ","fawuzan","01M7EAS4WP1G4JD4KG87P6PTK6",0,"MIT","https:\u002F\u002Fgithub.com\u002Ffozagtx\u002FBuildOS-workflow\u002Fblob\u002Fmaster\u002Fskills\u002Fcalle-script-advisor\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: calle-script-advisor\ndescription: Draft and check CALL-E phone-call task text and result schemas for clarity, safety, and extraction quality before any call is placed.\nlicense: MIT\n---\n\n# CALL-E Script Advisor\n\nCALL-E's `task` field is free-form natural language, and its quality determines whether a call succeeds. A vague task produces a vague conversation, low extraction confidence, and an unusable result - and by the time that is visible, the call has already been placed and paid for. This skill turns CALL-E's own API guidance into an executable check that catches that before the call happens.\n\n## When To Use\n\nUse this skill whenever you are drafting or reviewing a CALL-E `task` and `result_schema`, before any call is placed. That includes writing a new call from scratch, adapting an existing task for a new scenario, and reviewing a task or schema someone else wrote.\n\n## The Drafting Procedure\n\nBefore writing any text, gather:\n\n1. **The goal** - why this call is happening, in one sentence.\n2. **The single decision the call must establish** - the one thing that determines what happens next. If there seem to be several, pick the one that matters most and treat the rest as optional context.\n3. **Who is calling and why** - the identification line the agent should open with: who they are, who they are calling on behalf of (if anyone), and the reason for the call.\n4. **How to close the call** - the instruction that ends the conversation cleanly once the ask is resolved.\n5. **What to do on voicemail** - whether to leave a message, what it should say, and whether to try again.\n\nThen, in order:\n\n1. Write the `task` text: identification, purpose, the single ask, edge-case handling, and the close. See `references\u002Fscript-patterns.md` for the anatomy and a before\u002Fafter rewrite.\n2. Write the `result_schema` to capture exactly the decision the call must establish - not everything that was discussed, just the answer this call exists to produce.\n\n## The Checking Step\n\nRun `scripts\u002Fcheck-call-script.mjs` against the task and schema, and iterate until there are no errors:\n\n```bash\nnode scripts\u002Fcheck-call-script.mjs --task-file \u003Cpath> --schema-file \u003Cpath>\nnode scripts\u002Fcheck-call-script.mjs --task \"...\" --schema '{...}'\n```\n\nBoth arguments are optional independently - lint a task alone, a schema alone, or both. The script prints findings grouped by severity, a score out of 100, and exits 1 if any error-severity finding exists, so it can gate a workflow.\n\nErrors are not negotiable - fix every one. Warnings are judgement calls: read the suggestion, decide whether it applies to this call, and either fix it or consciously accept it. A warning left in place should be a deliberate choice, not an oversight.\n\nSee `references\u002Fexamples.md` for three complete worked examples that pass the linter with zero errors.\n\n## Rules That Are Not Negotiable\n\n- Never invent a phone number. Use only the number the user provided or that the calling system resolved.\n- Never infer region, locale, or timezone from a phone number.\n- Never solicit sensitive personal data: Social Security numbers, credit card or bank account numbers, CVVs, PINs, passwords, dates of birth, or a mother's maiden name. See `references\u002Fsafety.md`.\n- Always include an `unknown` (or `unclear` \u002F `not_stated` \u002F `undetermined`) enum member for anything the call may fail to establish. CALL-E's own docs recommend this explicitly, and it is what lets a downstream integration tell \"the answer is no\" apart from \"there was no answer\" - the sibling `plugins\u002Fzapier-calle` refuses to mark a call actionable when a required field comes back with one of these values, so the enum member is not decoration.\n- Ask the schema for its own evidence. Beside any field an automation will act on, add a `\u003Cfield>_quote` string described as *the recipient's exact words that establish the answer above*. It costs nothing - the extraction model is already reading the transcript - and it is the only thing that separates an answer drawn from the call from one drawn from thin air, since both arrive as equally well-formed JSON with equally high confidence. The sibling `plugins\u002Fzapier-calle` verifies that quote against the transcript and sends the call to human review when it appears nowhere the recipient spoke. Ask for a full spoken sentence rather than a word: a one-word quote can match by coincidence. **List the `_quote` field in `required` alongside the field it supports.** A quote the model may omit is a check that switches itself off on exactly the call that had no evidence to offer, since a missing key is nothing for a verifier to examine; requiring it turns a silent pass into a loud failure.\n- Mark a field `required` only when the workflow genuinely cannot proceed without it. `required` is a contract: an integration that checks it will send the whole call to human review when the field is absent or unknown. Requiring a nice-to-have field turns every partially-successful call into manual work.\n- Never let the script imply a commitment the caller cannot honour - no promised callback times, approvals, or guarantees the agent is not authorized to make.\n\nRead `references\u002Fsafety.md` before drafting any task that touches consent, disclosure, calling windows, or a do-not-call request.\n\n## Progressive Disclosure\n\nThis file stays focused on the workflow. Detail lives in `references\u002F`:\n\n- `references\u002Fscript-patterns.md` - the anatomy of a good task, with a before\u002Fafter rewrite.\n- `references\u002Fsafety.md` - consent, disclosure, sensitive data, calling windows, and do-not-call handling.\n- `references\u002Fexamples.md` - three worked examples (appointment confirmation, on-call acknowledgement, lead qualification), each verified against the linter.\n","# CALL-E Script Advisor\n\nCALL-E's `task` field is free-form natural language, and its quality determines whether a call succeeds. A vague task produces a vague conversation, low extraction confidence, and an unusable result - and by the time that is visible, the call has already been placed and paid for. This skill turns CALL-E's own API guidance into an executable check that catches that before the call happens.\n\n## When To Use\n\nUse this skill whenever you are drafting or reviewing a CALL-E `task` and `result_schema`, before any call is placed. That includes writing a new call from scratch, adapting an existing task for a new scenario, and reviewing a task or schema someone else wrote.\n\n## The Drafting Procedure\n\nBefore writing any text, gather:\n\n1. **The goal** - why this call is happening, in one sentence.\n2. **The single decision the call must establish** - the one thing that determines what happens next. If there seem to be several, pick the one that matters most and treat the rest as optional context.\n3. **Who is calling and why** - the identification line the agent should open with: who they are, who they are calling on behalf of (if anyone), and the reason for the call.\n4. **How to close the call** - the instruction that ends the conversation cleanly once the ask is resolved.\n5. **What to do on voicemail** - whether to leave a message, what it should say, and whether to try again.\n\nThen, in order:\n\n1. Write the `task` text: identification, purpose, the single ask, edge-case handling, and the close. See `references\u002Fscript-patterns.md` for the anatomy and a before\u002Fafter rewrite.\n2. Write the `result_schema` to capture exactly the decision the call must establish - not everything that was discussed, just the answer this call exists to produce.\n\n## The Checking Step\n\nRun `scripts\u002Fcheck-call-script.mjs` against the task and schema, and iterate until there are no errors:\n\n```bash\nnode scripts\u002Fcheck-call-script.mjs --task-file \u003Cpath> --schema-file \u003Cpath>\nnode scripts\u002Fcheck-call-script.mjs --task \"...\" --schema '{...}'\n```\n\nBoth arguments are optional independently - lint a task alone, a schema alone, or both. The script prints findings grouped by severity, a score out of 100, and exits 1 if any error-severity finding exists, so it can gate a workflow.\n\nErrors are not negotiable - fix every one. Warnings are judgement calls: read the suggestion, decide whether it applies to this call, and either fix it or consciously accept it. A warning left in place should be a deliberate choice, not an oversight.\n\nSee `references\u002Fexamples.md` for three complete worked examples that pass the linter with zero errors.\n\n## Rules That Are Not Negotiable\n\n- Never invent a phone number. Use only the number the user provided or that the calling system resolved.\n- Never infer region, locale, or timezone from a phone number.\n- Never solicit sensitive personal data: Social Security numbers, credit card or bank account numbers, CVVs, PINs, passwords, dates of birth, or a mother's maiden name. See `references\u002Fsafety.md`.\n- Always include an `unknown` (or `unclear` \u002F `not_stated` \u002F `undetermined`) enum member for anything the call may fail to establish. CALL-E's own docs recommend this explicitly, and it is what lets a downstream integration tell \"the answer is no\" apart from \"there was no answer\" - the sibling `plugins\u002Fzapier-calle` refuses to mark a call actionable when a required field comes back with one of these values, so the enum member is not decoration.\n- Ask the schema for its own evidence. Beside any field an automation will act on, add a `\u003Cfield>_quote` string described as *the recipient's exact words that establish the answer above*. It costs nothing - the extraction model is already reading the transcript - and it is the only thing that separates an answer drawn from the call from one drawn from thin air, since both arrive as equally well-formed JSON with equally high confidence. The sibling `plugins\u002Fzapier-calle` verifies that quote against the transcript and sends the call to human review when it appears nowhere the recipient spoke. Ask for a full spoken sentence rather than a word: a one-word quote can match by coincidence. **List the `_quote` field in `required` alongside the field it supports.** A quote the model may omit is a check that switches itself off on exactly the call that had no evidence to offer, since a missing key is nothing for a verifier to examine; requiring it turns a silent pass into a loud failure.\n- Mark a field `required` only when the workflow genuinely cannot proceed without it. `required` is a contract: an integration that checks it will send the whole call to human review when the field is absent or unknown. Requiring a nice-to-have field turns every partially-successful call into manual work.\n- Never let the script imply a commitment the caller cannot honour - no promised callback times, approvals, or guarantees the agent is not authorized to make.\n\nRead `references\u002Fsafety.md` before drafting any task that touches consent, disclosure, calling windows, or a do-not-call request.\n\n## Progressive Disclosure\n\nThis file stays focused on the workflow. Detail lives in `references\u002F`:\n\n- `references\u002Fscript-patterns.md` - the anatomy of a good task, with a before\u002Fafter rewrite.\n- `references\u002Fsafety.md` - consent, disclosure, sensitive data, calling windows, and do-not-call handling.\n- `references\u002Fexamples.md` - three worked examples (appointment confirmation, on-call acknowledgement, lead qualification), each verified against the linter.\n",{"name":5,"license":15,"description":7},"master","8c91ae30409640de28e218b3e9c7fe01c01d257b","skills\u002Fcalle-script-advisor","https:\u002F\u002Fgithub.com\u002Ffozagtx\u002FBuildOS-workflow","https:\u002F\u002Fgithub.com\u002Ffozagtx","hi.fawuzanpima@gmail.com","Forward deployed","2026-10-08 00:13:28",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add fozagtx\u002FBuildOS-workflow --skill calle-script-advisor",{"tool":38,"command":39},"bunx","bunx skills add fozagtx\u002FBuildOS-workflow --skill calle-script-advisor",{"tool":41,"command":42},"pnpm","pnpm dlx skills add fozagtx\u002FBuildOS-workflow --skill calle-script-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffozagtx\u002FBuildOS-workflow\u002Fblob\u002Fmaster\u002Fskills\u002Fcalle-script-advisor\u002FSKILL.md",true,[46,52,56,60,66],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fexamples.md","REFERENCE","参考文档",4885,"https:\u002F\u002Fgithub.com\u002Ffozagtx\u002FBuildOS-workflow\u002Fblob\u002Fmaster\u002Fskills\u002Fcalle-script-advisor\u002Freferences\u002Fexamples.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fsafety.md",3953,"https:\u002F\u002Fgithub.com\u002Ffozagtx\u002FBuildOS-workflow\u002Fblob\u002Fmaster\u002Fskills\u002Fcalle-script-advisor\u002Freferences\u002Fsafety.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fscript-patterns.md",3515,"https:\u002F\u002Fgithub.com\u002Ffozagtx\u002FBuildOS-workflow\u002Fblob\u002Fmaster\u002Fskills\u002Fcalle-script-advisor\u002Freferences\u002Fscript-patterns.md",{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"scripts\u002Fcheck-call-script.mjs","SCRIPT","脚本",19086,"https:\u002F\u002Fgithub.com\u002Ffozagtx\u002FBuildOS-workflow\u002Fblob\u002Fmaster\u002Fskills\u002Fcalle-script-advisor\u002Fscripts\u002Fcheck-call-script.mjs",{"path":67,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":68,"sourceHtmlUrl":69},"scripts\u002Fcheck-call-script.test.mjs",11624,"https:\u002F\u002Fgithub.com\u002Ffozagtx\u002FBuildOS-workflow\u002Fblob\u002Fmaster\u002Fskills\u002Fcalle-script-advisor\u002Fscripts\u002Fcheck-call-script.test.mjs",[71,78,85,92,99,108],{"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},"01M7EE49XAN8GE213J691P3RZ9","xitter","Interact with X\u002FTwitter via the x-cli terminal client using official X API credentials. Use for posting, reading timelines, searching tweets, liking, retweeting, bookmarks, mentions, and user lookups.","https:\u002F\u002Fgithub.com\u002Ffozagtx\u002FBuildOS-workflow\u002Fblob\u002Fmaster\u002Fskills\u002Fxitter\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},"01M7EE3TMR3CR7HR7HTCAKPTTR","writing-plans","Use when you have a spec or requirements for a multi-step task. Creates comprehensive implementation plans with bite-sized tasks, exact file paths, and complete code examples.","https:\u002F\u002Fgithub.com\u002Ffozagtx\u002FBuildOS-workflow\u002Fblob\u002Fmaster\u002Fskills\u002Fwriting-plans\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},"01M7EE3AJ6V2VBVAX1WTV7M447","whisper","OpenAI's general-purpose speech recognition model. Supports 99 languages, transcription, translation to English, and language identification. Six model sizes from tiny (39M params) to large (1550M params). Use for speech-to-text, podcast transcription, or multilingual audio processing. Best for robust, multilingual ASR.","https:\u002F\u002Fgithub.com\u002Ffozagtx\u002FBuildOS-workflow\u002Fblob\u002Fmaster\u002Fskills\u002Fwhisper\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},"01M7EE36AAP5THSCQAHH6JCWVV","weights-and-biases","Track ML experiments with automatic logging, visualize training in real-time, optimize hyperparameters with sweeps, and manage model registry with W&B - collaborative MLOps platform","https:\u002F\u002Fgithub.com\u002Ffozagtx\u002FBuildOS-workflow\u002Fblob\u002Fmaster\u002Fskills\u002Fweights-and-biases\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":103,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7EE30R3S4EAK1FWJEBG7MW9","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Ffozagtx\u002FBuildOS-workflow\u002Fblob\u002Fmaster\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Ffozagtx\u002FBuildOS-workflow\u002Fblob\u002Fmaster\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7EE2X3PJ0ZJR0JJNF2M4NS5","web-pentest","Authorized web pentest: recon, proof-based exploits, report.","https:\u002F\u002Fgithub.com\u002Ffozagtx\u002FBuildOS-workflow\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-pentest\u002FSKILL.md",[],[]]