[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EB575KVVP8P9FDNAMWY0D0":3,"skill-same:01M7EB575KVVP8P9FDNAMWY0D0":60},{"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},"01M7EB575KVVP8P9FDNAMWY0D0","carecall-missed-appointment",null,"Recover missed healthcare appointments through a safe administrative CALL-E conversation that verifies the patient, offers available rescheduling slots, confirms the selected slot, and returns a structured recovery outcome for a downstream appointment system.","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\u002Fcarecall-missed-appointment\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: carecall-missed-appointment\ndescription: Recover missed healthcare appointments through a safe administrative CALL-E conversation that verifies the patient, offers available rescheduling slots, confirms the selected slot, and returns a structured recovery outcome for a downstream appointment system.\nlicense: MIT\n---\n\nThe reference workflow is designed to:\n\n1. Confirm the intended patient.\n2. Inform them that they were unable to attend their appointment.\n3. Ask whether they would like to reschedule.\n4. Offer available appointment slots supplied by the host system.\n5. Confirm the slot selected by the patient.\n6. Return a structured result that a host system can use to update the appointment.\n\nThis is a workflow skill, not a medical assistant and not a replacement for a clinical professional.\n\nThis repository contribution is reference workflow documentation. It does not itself execute CALL-E calls.\n\nA host application is responsible for integrating with CALL-E, explicitly authorizing each real call, supplying the destination phone number and appointment data, handling credentials, preventing duplicate calls, and applying the returned structured result.\n\nAny runnable CareCall implementation lives outside this skill package and must provide its own safe default, such as dry-run, fake-server, or explicit opt-in before placing a real call.\n\n---\n\n# CareCall — Missed Appointment Recovery\n\n## Why this exists\n\nMissed healthcare appointments create administrative overhead for clinics and can leave appointment slots unused.\n\n`carecall-missed-appointment` automates the administrative recovery workflow after a patient misses an appointment.\n\nThe skill places an outbound CALL-E call to:\n\n1. Confirm the intended patient.\n2. Inform them that they were unable to attend their appointment.\n3. Ask whether they would like to reschedule.\n4. Offer available appointment slots.\n5. Confirm the slot selected by the patient.\n6. Return a structured result that a host system can use to update the appointment.\n\nThis is a workflow skill, not a medical assistant and not a replacement for a clinical professional.\n\nIt wraps CALL-E's existing one-off call API and structured-result capability.\n\n## When To Use\n\nUse this skill when:\n\n- a patient has missed an existing healthcare appointment\n- the clinic wants to proactively offer rescheduling\n- available appointment slots are known\n- the result needs to be written back to an appointment or scheduling system\n- the workflow needs a structured outcome such as `RESCHEDULED`, `DECLINED`, or `CALLBACK_REQUESTED`\n\n## When Not To Use\n\nDo not use this skill to:\n\n- provide medical advice\n- diagnose symptoms or conditions\n- interpret test results\n- recommend treatment\n- triage medical conditions\n- discuss unnecessary clinical information\n- contact a person whose phone number was not explicitly provided\n- invent appointment availability\n- disclose appointment information before appropriate patient verification\n- pressure a patient into rescheduling\n- make clinical decisions\n\n## Required Input\n\nThe host system should provide:\n\n- `patient_name`\n- `phone_number` in E.164 format\n- `missed_appointment_date`\n- `missed_appointment_time`\n- `available_slots`\n\nEach available slot should contain a specific date and time.\n\nThe host system must obtain and provide the correct appointment information. The skill must not invent or infer appointment details.\n\n## Core Workflow\n\n1. Receive the missed appointment details from the host system.\n\n2. Confirm that the recipient is the intended patient before disclosing appointment details.\n\n3. Explain that the patient was unable to attend their appointment.\n\n4. Ask whether they would like to reschedule.\n\n5. If the patient declines:\n   - respect the decision\n   - do not pressure them\n   - return `DECLINED`\n\n6. If the patient wants to reschedule:\n   - present only the available slots supplied by the host system\n   - allow the patient to select a slot\n   - confirm the selected date and time\n\n7. If the patient explicitly confirms the selected slot:\n   - return `RESCHEDULED`\n   - include the selected slot\n\n8. If the patient asks to be contacted later:\n   - return `CALLBACK_REQUESTED`\n\n9. If the recipient is not the intended patient:\n   - do not disclose appointment information\n   - return `WRONG_PERSON`\n\n10. If the patient raises a medical concern:\n    - do not provide medical advice\n    - stop the normal scheduling flow\n    - return `CLINICAL_FOLLOWUP_REQUIRED`\n\n11. If an urgent or potentially dangerous situation is raised:\n    - stop the scheduling workflow\n    - follow the clinic's approved emergency escalation policy\n    - return `SAFETY_ESCALATION`\n\n12. If the conversation cannot establish a reliable outcome:\n    - return `UNKNOWN`\n    - do not guess the result\n\n## Conversation Guidelines\n\nThe agent should be:\n\n- polite\n- concise\n- calm\n- empathetic\n- conversational\n- non-judgmental\n\nUse natural language rather than requiring exact yes\u002Fno responses.\n\nFor example, responses such as:\n\n- \"Yes, please.\"\n- \"That would be great.\"\n- \"Sure, let's move it.\"\n- \"I can't make that time.\"\n\nshould be understood naturally.\n\nDo not repeatedly ask a question when the patient has already answered it.\n\nDo not force the patient to repeat information unnecessarily.\n\nA suitable opening is:\n\n> \"Hi, is this [patient first name]?\"\n\nAfter appropriate verification:\n\n> \"I'm calling from CareCall about your missed appointment on [date] at [time]. We'd be happy to help arrange another time if you'd like.\"\n\nAvoid judgmental language such as:\n\n> \"Why did you miss your appointment?\"\n\n## Safety Rules\n\n### Administrative-only scope\n\nThe agent must only perform appointment coordination.\n\nIt must never:\n\n- diagnose\n- interpret symptoms\n- recommend medication\n- recommend treatment\n- interpret test results\n- provide clinical instructions\n\n### Patient verification\n\nDo not disclose unnecessary appointment information to an unverified person.\n\nIf the recipient is not the intended patient, end the appointment-recovery conversation without revealing sensitive details.\n\n### Clinical concerns\n\nIf the patient introduces a medical concern, do not attempt to answer it.\n\nStop the scheduling workflow and mark:\n\n`CLINICAL_FOLLOWUP_REQUIRED`\n\nThe host system can then route the case to appropriate clinic staff.\n\n### Safety escalation\n\nIf the patient describes a potentially urgent situation, do not attempt medical triage.\n\nStop the appointment workflow and follow the healthcare organization's approved emergency escalation process.\n\n### No pressure\n\nThe patient may decline rescheduling.\n\nThe agent must accept the decision without persuasion.\n\n### Appointment availability\n\nThe agent may only offer slots supplied by the host system.\n\nIt must never invent, modify, or promise availability.\n\n### Real-world call safety\n\nPhone calls are real-world side effects.\n\nThe host system must explicitly authorize the recovery workflow before placing the call.\n\nThe phone number must be explicitly supplied by the host system and must not be guessed.\n\nPhone numbers should be masked in logs and user-facing output.\n\n### Credentials\n\nNever expose CALL-E API keys, access tokens, or other credentials in logs, transcripts, responses, or committed files.\n\n## Structured Result\n\n## References\n\nFor detailed guidance, load these references when needed:\n\n- `references\u002Fresult-schema.md` — structured result fields, allowed values, validation rules, and examples.\n- `references\u002Fsafety.md` — detailed safety, verification, escalation, and data-minimization rules.\n\nThe skill returns a structured result containing:\n\n- `outcome`\n- `patient_confirmed`\n- `follow_up_required`\n- `selected_slot`\n\nPossible outcomes:\n\n- `RESCHEDULED`\n- `DECLINED`\n- `CALLBACK_REQUESTED`\n- `NO_ANSWER`\n- `WRONG_PERSON`\n- `CLINICAL_FOLLOWUP_REQUIRED`\n- `SAFETY_ESCALATION`\n- `UNKNOWN`\n\n`selected_slot` should contain `NONE` when no slot was selected.\n\nThe host application is responsible for applying the result to the underlying appointment system.\n\n## Success Criteria\n\nA call may be considered `RESCHEDULED` only when:\n\n1. the intended patient was appropriately verified\n2. the patient explicitly agreed to reschedule\n3. an available slot was selected\n4. the selected slot was explicitly confirmed\n\nA high-confidence CALL-E result should be preferred, but the host system must not fabricate an outcome when the conversation is ambiguous.\n\n## Example Result\n\n```json\n{\n  \"outcome\": \"RESCHEDULED\",\n  \"patient_confirmed\": \"YES\",\n  \"follow_up_required\": \"NO\",\n  \"selected_slot\": \"SLOT-003\"\n}\n","The reference workflow is designed to:\n\n1. Confirm the intended patient.\n2. Inform them that they were unable to attend their appointment.\n3. Ask whether they would like to reschedule.\n4. Offer available appointment slots supplied by the host system.\n5. Confirm the slot selected by the patient.\n6. Return a structured result that a host system can use to update the appointment.\n\nThis is a workflow skill, not a medical assistant and not a replacement for a clinical professional.\n\nThis repository contribution is reference workflow documentation. It does not itself execute CALL-E calls.\n\nA host application is responsible for integrating with CALL-E, explicitly authorizing each real call, supplying the destination phone number and appointment data, handling credentials, preventing duplicate calls, and applying the returned structured result.\n\nAny runnable CareCall implementation lives outside this skill package and must provide its own safe default, such as dry-run, fake-server, or explicit opt-in before placing a real call.\n\n---\n\n# CareCall — Missed Appointment Recovery\n\n## Why this exists\n\nMissed healthcare appointments create administrative overhead for clinics and can leave appointment slots unused.\n\n`carecall-missed-appointment` automates the administrative recovery workflow after a patient misses an appointment.\n\nThe skill places an outbound CALL-E call to:\n\n1. Confirm the intended patient.\n2. Inform them that they were unable to attend their appointment.\n3. Ask whether they would like to reschedule.\n4. Offer available appointment slots.\n5. Confirm the slot selected by the patient.\n6. Return a structured result that a host system can use to update the appointment.\n\nThis is a workflow skill, not a medical assistant and not a replacement for a clinical professional.\n\nIt wraps CALL-E's existing one-off call API and structured-result capability.\n\n## When To Use\n\nUse this skill when:\n\n- a patient has missed an existing healthcare appointment\n- the clinic wants to proactively offer rescheduling\n- available appointment slots are known\n- the result needs to be written back to an appointment or scheduling system\n- the workflow needs a structured outcome such as `RESCHEDULED`, `DECLINED`, or `CALLBACK_REQUESTED`\n\n## When Not To Use\n\nDo not use this skill to:\n\n- provide medical advice\n- diagnose symptoms or conditions\n- interpret test results\n- recommend treatment\n- triage medical conditions\n- discuss unnecessary clinical information\n- contact a person whose phone number was not explicitly provided\n- invent appointment availability\n- disclose appointment information before appropriate patient verification\n- pressure a patient into rescheduling\n- make clinical decisions\n\n## Required Input\n\nThe host system should provide:\n\n- `patient_name`\n- `phone_number` in E.164 format\n- `missed_appointment_date`\n- `missed_appointment_time`\n- `available_slots`\n\nEach available slot should contain a specific date and time.\n\nThe host system must obtain and provide the correct appointment information. The skill must not invent or infer appointment details.\n\n## Core Workflow\n\n1. Receive the missed appointment details from the host system.\n\n2. Confirm that the recipient is the intended patient before disclosing appointment details.\n\n3. Explain that the patient was unable to attend their appointment.\n\n4. Ask whether they would like to reschedule.\n\n5. If the patient declines:\n   - respect the decision\n   - do not pressure them\n   - return `DECLINED`\n\n6. If the patient wants to reschedule:\n   - present only the available slots supplied by the host system\n   - allow the patient to select a slot\n   - confirm the selected date and time\n\n7. If the patient explicitly confirms the selected slot:\n   - return `RESCHEDULED`\n   - include the selected slot\n\n8. If the patient asks to be contacted later:\n   - return `CALLBACK_REQUESTED`\n\n9. If the recipient is not the intended patient:\n   - do not disclose appointment information\n   - return `WRONG_PERSON`\n\n10. If the patient raises a medical concern:\n    - do not provide medical advice\n    - stop the normal scheduling flow\n    - return `CLINICAL_FOLLOWUP_REQUIRED`\n\n11. If an urgent or potentially dangerous situation is raised:\n    - stop the scheduling workflow\n    - follow the clinic's approved emergency escalation policy\n    - return `SAFETY_ESCALATION`\n\n12. If the conversation cannot establish a reliable outcome:\n    - return `UNKNOWN`\n    - do not guess the result\n\n## Conversation Guidelines\n\nThe agent should be:\n\n- polite\n- concise\n- calm\n- empathetic\n- conversational\n- non-judgmental\n\nUse natural language rather than requiring exact yes\u002Fno responses.\n\nFor example, responses such as:\n\n- \"Yes, please.\"\n- \"That would be great.\"\n- \"Sure, let's move it.\"\n- \"I can't make that time.\"\n\nshould be understood naturally.\n\nDo not repeatedly ask a question when the patient has already answered it.\n\nDo not force the patient to repeat information unnecessarily.\n\nA suitable opening is:\n\n> \"Hi, is this [patient first name]?\"\n\nAfter appropriate verification:\n\n> \"I'm calling from CareCall about your missed appointment on [date] at [time]. We'd be happy to help arrange another time if you'd like.\"\n\nAvoid judgmental language such as:\n\n> \"Why did you miss your appointment?\"\n\n## Safety Rules\n\n### Administrative-only scope\n\nThe agent must only perform appointment coordination.\n\nIt must never:\n\n- diagnose\n- interpret symptoms\n- recommend medication\n- recommend treatment\n- interpret test results\n- provide clinical instructions\n\n### Patient verification\n\nDo not disclose unnecessary appointment information to an unverified person.\n\nIf the recipient is not the intended patient, end the appointment-recovery conversation without revealing sensitive details.\n\n### Clinical concerns\n\nIf the patient introduces a medical concern, do not attempt to answer it.\n\nStop the scheduling workflow and mark:\n\n`CLINICAL_FOLLOWUP_REQUIRED`\n\nThe host system can then route the case to appropriate clinic staff.\n\n### Safety escalation\n\nIf the patient describes a potentially urgent situation, do not attempt medical triage.\n\nStop the appointment workflow and follow the healthcare organization's approved emergency escalation process.\n\n### No pressure\n\nThe patient may decline rescheduling.\n\nThe agent must accept the decision without persuasion.\n\n### Appointment availability\n\nThe agent may only offer slots supplied by the host system.\n\nIt must never invent, modify, or promise availability.\n\n### Real-world call safety\n\nPhone calls are real-world side effects.\n\nThe host system must explicitly authorize the recovery workflow before placing the call.\n\nThe phone number must be explicitly supplied by the host system and must not be guessed.\n\nPhone numbers should be masked in logs and user-facing output.\n\n### Credentials\n\nNever expose CALL-E API keys, access tokens, or other credentials in logs, transcripts, responses, or committed files.\n\n## Structured Result\n\n## References\n\nFor detailed guidance, load these references when needed:\n\n- `references\u002Fresult-schema.md` — structured result fields, allowed values, validation rules, and examples.\n- `references\u002Fsafety.md` — detailed safety, verification, escalation, and data-minimization rules.\n\nThe skill returns a structured result containing:\n\n- `outcome`\n- `patient_confirmed`\n- `follow_up_required`\n- `selected_slot`\n\nPossible outcomes:\n\n- `RESCHEDULED`\n- `DECLINED`\n- `CALLBACK_REQUESTED`\n- `NO_ANSWER`\n- `WRONG_PERSON`\n- `CLINICAL_FOLLOWUP_REQUIRED`\n- `SAFETY_ESCALATION`\n- `UNKNOWN`\n\n`selected_slot` should contain `NONE` when no slot was selected.\n\nThe host application is responsible for applying the result to the underlying appointment system.\n\n## Success Criteria\n\nA call may be considered `RESCHEDULED` only when:\n\n1. the intended patient was appropriately verified\n2. the patient explicitly agreed to reschedule\n3. an available slot was selected\n4. the selected slot was explicitly confirmed\n\nA high-confidence CALL-E result should be preferred, but the host system must not fabricate an outcome when the conversation is ambiguous.\n\n## Example Result\n\n```json\n{\n  \"outcome\": \"RESCHEDULED\",\n  \"patient_confirmed\": \"YES\",\n  \"follow_up_required\": \"NO\",\n  \"selected_slot\": \"SLOT-003\"\n}\n",{"name":5,"license":15,"description":7},"master","8c91ae30409640de28e218b3e9c7fe01c01d257b","skills\u002Fcarecall-missed-appointment","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 carecall-missed-appointment",{"tool":38,"command":39},"bunx","bunx skills add fozagtx\u002FBuildOS-workflow --skill carecall-missed-appointment",{"tool":41,"command":42},"pnpm","pnpm dlx skills add fozagtx\u002FBuildOS-workflow --skill carecall-missed-appointment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffozagtx\u002FBuildOS-workflow\u002Fblob\u002Fmaster\u002Fskills\u002Fcarecall-missed-appointment\u002FSKILL.md",true,[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fexamples.md","REFERENCE","参考文档",1687,"https:\u002F\u002Fgithub.com\u002Ffozagtx\u002FBuildOS-workflow\u002Fblob\u002Fmaster\u002Fskills\u002Fcarecall-missed-appointment\u002Freferences\u002Fexamples.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fresult-schema.md",2483,"https:\u002F\u002Fgithub.com\u002Ffozagtx\u002FBuildOS-workflow\u002Fblob\u002Fmaster\u002Fskills\u002Fcarecall-missed-appointment\u002Freferences\u002Fresult-schema.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fsafety.md",6008,"https:\u002F\u002Fgithub.com\u002Ffozagtx\u002FBuildOS-workflow\u002Fblob\u002Fmaster\u002Fskills\u002Fcarecall-missed-appointment\u002Freferences\u002Fsafety.md",[61,68,75,82,89,98],{"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},"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":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},"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":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},"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":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},"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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",[],[]]