[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DGW5ZBV5WD5HAENJMRM3TS":3,"skill-same:01M7DGW5ZBV5WD5HAENJMRM3TS":57},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M7DGW5ZBV5WD5HAENJMRM3TS","bug-hunt-swarm",null,"Parallel read-only multi-agent root-cause investigation for bugs, regressions, crashes, flaky behavior, or unexplained failures. Use when the user asks to investigate a bug, find the root cause, trace a regression, understand why something broke, or wants a ranked diagnosis with the...","Hazek-dc\u002FPresensiGuru_FaceNet_EMAR","Hazek-dc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75208960?v=4","01M7DEQV5B4YGS86A81DYH81DR","Hazek","01M7DEQV5XP4TM0C6NTHXCXCHR",1,"MIT","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbug-hunt-swarm\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bug-hunt-swarm\ndescription: Parallel read-only multi-agent root-cause investigation for bugs, regressions, crashes, flaky behavior, or unexplained failures. Use when the user asks to investigate a bug, find the root cause, trace a regression, understand why something broke, or wants a ranked diagnosis with the...\nrisk: unknown\nsource: https:\u002F\u002Fgithub.com\u002FDimillian\u002FSkills\u002Ftree\u002Fmain\u002Fbug-hunt-swarm\nsource_repo: Dimillian\u002FSkills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002FDimillian\u002FSkills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Bug Hunt Swarm\n## When to Use\n\nUse this skill when you need parallel read-only multi-agent root-cause investigation for bugs, regressions, crashes, flaky behavior, or unexplained failures. Use when the user asks to investigate a bug, find the root cause, trace a regression, understand why something broke, or wants a ranked diagnosis with the...\n\n\nInvestigate a bug with four read-only sub-agents in parallel, then have the main agent rank the likely causes and recommend the fastest path to prove or fix the issue. This skill is diagnosis-first: do not edit files or implement fixes as part of this workflow.\n\n## Step 1: Build the Bug Packet\n\nStart by collecting the smallest useful investigation packet:\n\n1. Symptom\n2. Expected behavior\n3. Actual behavior\n4. Reproduction steps, if known\n5. Scope of impact\n6. Relevant evidence, such as logs, stack traces, failing tests, screenshots, recent diffs, or environment details\n\nPrefer this source order:\n\n1. Direct user description\n2. Explicit files, stack traces, logs, tests, or screenshots provided by the user\n3. Current git changes or recent repo history when the bug appears regression-like\n4. The smallest relevant code path or subsystem surrounding the failure\n\nIf the bug report is underspecified, infer a minimal problem statement and say what is still unknown.\n\nBefore launching sub-agents, read the closest project instructions and relevant docs for the touched area, such as:\n\n- `AGENTS.md`\n- repo workflow docs\n- architecture, state, routing, schema, or runtime docs for the affected subsystem\n\n## Step 2: Bound the Investigation\n\nWrite a short investigation brief for the swarm:\n\n1. What appears broken\n2. What is not yet proven\n3. What part of the system is most likely involved\n4. What evidence already exists\n5. What kind of proof would count as confirmation\n\nUse read-only evidence gathering where useful:\n\n- `rg`, `git diff`, `git log`, `git show`\n- reading logs, crash traces, and config\n- existing test runs or the smallest safe reproduction command\n\nDo not edit files, inject new instrumentation, or implement fixes as part of this skill.\n\n## Step 3: Launch Four Read-Only Investigators in Parallel\n\nLaunch four sub-agents when the problem is large or ambiguous enough that parallel investigation helps. For a tiny and obvious issue, it is acceptable to investigate locally instead.\n\nFor every sub-agent:\n\n- give the same bug packet and investigation brief\n- state that the sub-agent is read-only\n- do not let the sub-agent edit files, run `apply_patch`, stage changes, commit, or perform any other state-mutating action\n- ask for concise investigation output only\n- ask for: hypothesis, supporting evidence, missing evidence, smallest proof step, and confidence\n- tell the sub-agent to avoid generic code quality feedback, nits, or speculative guesses without evidence\n- tell the sub-agent to send findings back to the main agent only\n\nUse these four investigation roles.\n\n### Sub-Agent 1: Reproduction and Scope Investigation\n\nClarify the exact failure shape and its boundaries.\n\nCheck for:\n\n1. The narrowest reliable trigger\n2. Conditions that make the bug appear or disappear\n3. Expected versus actual behavior at the failure boundary\n4. Whether the impact is local, cross-cutting, deterministic, or flaky\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `reviewer`\n\n### Sub-Agent 2: Code Path and Failure Seam Investigation\n\nTrace the most likely execution path and identify the seam where behavior diverges.\n\nCheck for:\n\n1. State transitions, lifecycle edges, or ordering problems\n2. Mismatched assumptions between caller and callee\n3. Data-flow or control-flow breaks\n4. The smallest code region most likely responsible for the failure\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `explorer` for broad tracing, or `reviewer` when a stronger local reasoning pass is more useful\n\n### Sub-Agent 3: Recent Change and Regression Investigation\n\nLook for likely regressors in nearby history or changed contracts.\n\nCheck for:\n\n1. Recent diffs that correlate with the symptom\n2. Config, flag, dependency, schema, or migration drift\n3. Partial updates where several entry points should have changed together\n4. Behavior changes that fit the timing of the bug report\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `reviewer`\n\n### Sub-Agent 4: Proof Plan and Observability Investigation\n\nDetermine the fastest way to confirm or reject the leading hypotheses.\n\nCheck for:\n\n1. The smallest existing test or reproduction that should fail\n2. The most useful current logs, traces, metrics, or assertions\n3. A minimal non-mutating command that could raise confidence quickly\n4. What evidence is missing and how to collect it without broad churn\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `reviewer`\n\nReport only hypotheses that materially improve the odds of finding the real cause. It is better to return two evidence-backed theories than six vague guesses.\n\n## Step 4: Synthesize Ranked Hypotheses\n\nThe main agent owns synthesis. Treat sub-agent output as raw investigation input, not final output.\n\nMerge and rank the hypotheses:\n\n- combine duplicates\n- discard weak speculation\n- prefer evidence over elegance\n- separate likely root causes from mere contributing factors\n- keep alternate theories only when they remain plausible\n\nNormalize the surviving hypotheses into this shape:\n\n1. Hypothesis\n2. Supporting evidence\n3. Missing or conflicting evidence\n4. Smallest proof step\n5. Confidence: high, medium, or low\n\nIf the evidence is too weak for a real ranking, say so directly and present the leading open questions instead.\n\n## Step 5: Output a Clear Diagnosis Path\n\nPresent the result in this order:\n\n1. Most likely root cause\n2. Plausible alternate causes, if any\n3. Fastest proof step\n4. Recommended fix path\n5. Open questions or blockers\n\nWhen the fix is not yet clear, recommend the next proving step instead of pretending the diagnosis is complete.\n\nWhen helpful, group actions into:\n\n- `prove now`\n- `fix next`\n- `follow up later`\n\nDo not implement fixes as part of this skill. The output is a read-only diagnosis with a prioritized path forward.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Bug Hunt Swarm\n## When to Use\n\nUse this skill when you need parallel read-only multi-agent root-cause investigation for bugs, regressions, crashes, flaky behavior, or unexplained failures. Use when the user asks to investigate a bug, find the root cause, trace a regression, understand why something broke, or wants a ranked diagnosis with the...\n\n\nInvestigate a bug with four read-only sub-agents in parallel, then have the main agent rank the likely causes and recommend the fastest path to prove or fix the issue. This skill is diagnosis-first: do not edit files or implement fixes as part of this workflow.\n\n## Step 1: Build the Bug Packet\n\nStart by collecting the smallest useful investigation packet:\n\n1. Symptom\n2. Expected behavior\n3. Actual behavior\n4. Reproduction steps, if known\n5. Scope of impact\n6. Relevant evidence, such as logs, stack traces, failing tests, screenshots, recent diffs, or environment details\n\nPrefer this source order:\n\n1. Direct user description\n2. Explicit files, stack traces, logs, tests, or screenshots provided by the user\n3. Current git changes or recent repo history when the bug appears regression-like\n4. The smallest relevant code path or subsystem surrounding the failure\n\nIf the bug report is underspecified, infer a minimal problem statement and say what is still unknown.\n\nBefore launching sub-agents, read the closest project instructions and relevant docs for the touched area, such as:\n\n- `AGENTS.md`\n- repo workflow docs\n- architecture, state, routing, schema, or runtime docs for the affected subsystem\n\n## Step 2: Bound the Investigation\n\nWrite a short investigation brief for the swarm:\n\n1. What appears broken\n2. What is not yet proven\n3. What part of the system is most likely involved\n4. What evidence already exists\n5. What kind of proof would count as confirmation\n\nUse read-only evidence gathering where useful:\n\n- `rg`, `git diff`, `git log`, `git show`\n- reading logs, crash traces, and config\n- existing test runs or the smallest safe reproduction command\n\nDo not edit files, inject new instrumentation, or implement fixes as part of this skill.\n\n## Step 3: Launch Four Read-Only Investigators in Parallel\n\nLaunch four sub-agents when the problem is large or ambiguous enough that parallel investigation helps. For a tiny and obvious issue, it is acceptable to investigate locally instead.\n\nFor every sub-agent:\n\n- give the same bug packet and investigation brief\n- state that the sub-agent is read-only\n- do not let the sub-agent edit files, run `apply_patch`, stage changes, commit, or perform any other state-mutating action\n- ask for concise investigation output only\n- ask for: hypothesis, supporting evidence, missing evidence, smallest proof step, and confidence\n- tell the sub-agent to avoid generic code quality feedback, nits, or speculative guesses without evidence\n- tell the sub-agent to send findings back to the main agent only\n\nUse these four investigation roles.\n\n### Sub-Agent 1: Reproduction and Scope Investigation\n\nClarify the exact failure shape and its boundaries.\n\nCheck for:\n\n1. The narrowest reliable trigger\n2. Conditions that make the bug appear or disappear\n3. Expected versus actual behavior at the failure boundary\n4. Whether the impact is local, cross-cutting, deterministic, or flaky\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `reviewer`\n\n### Sub-Agent 2: Code Path and Failure Seam Investigation\n\nTrace the most likely execution path and identify the seam where behavior diverges.\n\nCheck for:\n\n1. State transitions, lifecycle edges, or ordering problems\n2. Mismatched assumptions between caller and callee\n3. Data-flow or control-flow breaks\n4. The smallest code region most likely responsible for the failure\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `explorer` for broad tracing, or `reviewer` when a stronger local reasoning pass is more useful\n\n### Sub-Agent 3: Recent Change and Regression Investigation\n\nLook for likely regressors in nearby history or changed contracts.\n\nCheck for:\n\n1. Recent diffs that correlate with the symptom\n2. Config, flag, dependency, schema, or migration drift\n3. Partial updates where several entry points should have changed together\n4. Behavior changes that fit the timing of the bug report\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `reviewer`\n\n### Sub-Agent 4: Proof Plan and Observability Investigation\n\nDetermine the fastest way to confirm or reject the leading hypotheses.\n\nCheck for:\n\n1. The smallest existing test or reproduction that should fail\n2. The most useful current logs, traces, metrics, or assertions\n3. A minimal non-mutating command that could raise confidence quickly\n4. What evidence is missing and how to collect it without broad churn\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `reviewer`\n\nReport only hypotheses that materially improve the odds of finding the real cause. It is better to return two evidence-backed theories than six vague guesses.\n\n## Step 4: Synthesize Ranked Hypotheses\n\nThe main agent owns synthesis. Treat sub-agent output as raw investigation input, not final output.\n\nMerge and rank the hypotheses:\n\n- combine duplicates\n- discard weak speculation\n- prefer evidence over elegance\n- separate likely root causes from mere contributing factors\n- keep alternate theories only when they remain plausible\n\nNormalize the surviving hypotheses into this shape:\n\n1. Hypothesis\n2. Supporting evidence\n3. Missing or conflicting evidence\n4. Smallest proof step\n5. Confidence: high, medium, or low\n\nIf the evidence is too weak for a real ranking, say so directly and present the leading open questions instead.\n\n## Step 5: Output a Clear Diagnosis Path\n\nPresent the result in this order:\n\n1. Most likely root cause\n2. Plausible alternate causes, if any\n3. Fastest proof step\n4. Recommended fix path\n5. Open questions or blockers\n\nWhen the fix is not yet clear, recommend the next proving step instead of pretending the diagnosis is complete.\n\nWhen helpful, group actions into:\n\n- `prove now`\n- `fix next`\n- `follow up later`\n\nDo not implement fixes as part of this skill. The output is a read-only diagnosis with a prioritized path forward.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"unknown","https:\u002F\u002Fgithub.com\u002FDimillian\u002FSkills\u002Ftree\u002Fmain\u002Fbug-hunt-swarm",1782864000000,"Dimillian\u002FSkills","community","https:\u002F\u002Fgithub.com\u002FDimillian\u002FSkills\u002Fblob\u002Fmain\u002FLICENSE","main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Fbug-hunt-swarm",0,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR","https:\u002F\u002Fgithub.com\u002FHazek-dc","2026-10-22 08:36:44",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill bug-hunt-swarm",{"tool":43,"command":44},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill bug-hunt-swarm",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill bug-hunt-swarm","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbug-hunt-swarm\u002FSKILL.md",true,[51],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"agents\u002Fopenai.yaml","REFERENCE","参考文档",261,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbug-hunt-swarm\u002Fagents\u002Fopenai.yaml",[58,65,72,79,86,93],{"skillNo":59,"name":60,"nameZh":6,"description":61,"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},"01M7DS6GGYRZAYD33PFPS8Z2T3","testing-best-practices","Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7DS6BC3AW7HTPRHE2TTVKWM","tailwindcss-development","Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex\u002Fgrid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3\u002Fv4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML\u002FCSS component, CSS file audits, build tool configuration, and vanilla CSS.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftailwindcss-development\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7DS66GE6B11MYJDVC74HXM4","laravel-best-practices","Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Flaravel-best-practices\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7DS5ZW717DMS6P1E90AQCKV","infer-conventions","Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai\u002Frules`, resolve mixed or conflicting patterns (e.g. \"are we using Form Requests or inline validation?\"), or onboard agents and teammates to \"how we do things here\". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai\u002Frules` files by hand.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finfer-conventions\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7DS5W12RGCVJTFQJ1N0GB8E","inertia-react-development","Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using \u003CLink>, \u003CForm>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finertia-react-development\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7DS5PVDPMPCWSK2RXPDC9BB","deploying-to-cloud","Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Fdeploying-to-cloud\u002FSKILL.md",[],[]]