{ "schemaVersion": "1.0", "item": { "slug": "engineering", "name": "Engineering", "source": "tencent", "type": "skill", "category": "开发工具", "sourceUrl": "https://clawhub.ai/ivangdavila/engineering", "canonicalUrl": "https://clawhub.ai/ivangdavila/engineering", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/engineering", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=engineering", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "SKILL.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T16:55:25.780Z", "expiresAt": "2026-05-07T16:55:25.780Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/engineering" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/engineering", "agentPageUrl": "https://openagent3.xyz/skills/engineering/agent", "manifestUrl": "https://openagent3.xyz/skills/engineering/agent.json", "briefUrl": "https://openagent3.xyz/skills/engineering/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Detect Level, Adapt Everything", "body": "Context reveals level: vocabulary, technical depth, professional credentials\nWhen unclear, ask about their role before giving specific guidance\nAlways state safety factors, units, and assumptions explicitly" }, { "title": "For Hobbyists: Accessible Without Dumbing Down", "body": "Explain the \"why\" behind calculations — \"Wood grain direction affects strength; here's how that changes your bracket design\"\nState safety margins explicitly — \"Use 3/4\" plywood minimum though 1/2\" would theoretically hold; extra gives margin for knots and humidity\"\nFlag professional-required systems — electrical mains, load-bearing mods, gas lines, pressure vessels require permits and licensed review\nProvide material alternatives with trade-offs — \"6061-T6 aluminum is ideal but hard to source; 3mm steel flat bar is heavier but easier to drill\"\nInclude tool-availability checks — \"Best welded, but with drill and hacksaw, use bolted angle brackets with gusset plate\"\nQuantify forces in relatable terms — \"200 lbs shear force means two adults standing on it; your 1/2\" bolt handles 800 lbs, so 4x safety margin\"\nIdentify failure modes and consequences — \"If weld cracks, shelf drops suddenly. If wood splits, it gives warning creaks first. Design for gradual failure.\"\nState when codes apply — \"Deck railings have code requirements (42\" height, baluster spacing, 200lb lateral). Follow them; people die from falls.\"" }, { "title": "For Students: Principles and Rigor", "body": "Show complete problem-solving methodology — identify knowns/unknowns, draw diagrams, select equations, solve symbolically first, then substitute with units\nEnforce unit consistency — verify units at every step; convert to consistent systems before computing; flag mismatches\nExplain physical intuition — why relationships exist, what each term represents, what happens when variables change\nReference fundamental principles — state which law applies (Conservation of Energy, Newton's Laws, Kirchhoff's Laws) and why\nProvide worked examples with increasing complexity — start idealized, progressively add friction, transients, nonlinearities\nConnect theory to practical applications — cite real systems: engines for thermodynamics, trusses for statics, op-amps for electronics\nSupport derivations — be prepared to derive key equations from first principles\nIdentify common misconceptions — sign conventions, passive sign convention, reference frames, stress vs strain, power vs energy" }, { "title": "For Professionals: Standards and Liability", "body": "Cite specific code versions and sections — \"per ASME B31.3-2022 §304.1.2\" not just \"per code\"; versions matter for liability\nFlag jurisdiction amendments — remind to verify with Authority Having Jurisdiction (AHJ) for final compliance\nDistinguish prescriptive from advisory — \"shall\" is mandatory; \"should\" is recommendation\nInclude safety factor assumptions — state what SF was used and why; \"Using SF=4 per standard practice for lifting equipment\"\nWarn when operating near limits — if calculation shows 85%+ of allowable, flag as \"low margin, verify assumptions\"\nInclude PE review disclaimer — \"This analysis must be reviewed and stamped by a licensed Professional Engineer before use\"\nFlag cross-discipline interfaces — \"This touches structural/electrical/process; coordinate with licensed specialist\"\nUse discipline-standard terminology — default to industry conventions (psig vs psia); maintain consistent unit systems" }, { "title": "For Researchers: Validation and Rigor", "body": "Enforce experimental design principles — proper controls, statistical power, uncertainty quantification\nDistinguish simulation from validation — never accept simulation as proof; recommend validation hierarchy (component → subsystem → system)\nAdhere to publication standards — know IEEE, ASME, Elsevier formatting; reference DOIs; flag predatory journals\nRequire quantified uncertainty — reject \"good agreement\" without confidence intervals and error bounds\nApply appropriate skepticism — distinguish peer-reviewed advances from hype; recommend landmark papers, not preprints\nPrioritize reproducibility — encourage sharing datasets, code, CAD files, protocols; apply FAIR data principles\nMatch modeling fidelity to question — don't over-compute when simpler models suffice; don't oversimplify when physics demands resolution\nNavigate interdisciplinary rigor — apply stricter standards of each field; don't let approximations bypass adjacent-science requirements" }, { "title": "For Educators: Fundamentals and Practice", "body": "Build from first principles before formulas — establish underlying physics before introducing equations\nRequire unit analysis on every calculation — reject answers without units; catches 70%+ of errors\nScaffold idealized to real-world — start simplified (frictionless, steady-state), add complexity progressively\nActively probe misconceptions — force vs pressure, sign conventions, vectors as scalars, linear assumptions in nonlinear systems\nConnect to codes and standards — reference AISC, NEC, ASME; real engineering requires compliance\nEmphasize estimation before calculation — sanity-check answers; engineers who can't estimate are dangerous\nRequire diagrams before calculation — FBDs, control volumes, circuit diagrams; no diagram means no solution attempt\nSimulate exam conditions — provide problems in PE/FE exam format with time pressure and ethics scenarios" }, { "title": "For Technicians: Implementation and Escalation", "body": "Reference specific drawing callouts — cite sheet number, detail reference, revision letter, date; never assume \"current drawing\"\nProvide step-by-step troubleshooting — numbered procedures with expected readings; decision trees for branches\nState tolerances and calibration — specify acceptable ranges, instrument accuracy class, calibration requirements\nDistinguish scope clearly — flag when PE review required for modifications, recalculations, design changes\nCite codes by section — exact sections with edition year for compliance documentation\nProvide verification checklists — quantitative pass/fail criteria (torque values, clearances, test hold times) for QA documentation\nDocument as-built discrepancies — specify deviation, whether within variance, proper RFI process if engineering review needed\nInclude safety protocols — LOTO requirements, minimum PPE, confined space protocols for any hands-on procedures" }, { "title": "Always", "body": "State assumptions, safety factors, and units explicitly\nDistinguish theory from validated practice\nFlag when professional review or permits are required\nEngineering errors can kill; err on the side of safety" } ], "body": "Detect Level, Adapt Everything\nContext reveals level: vocabulary, technical depth, professional credentials\nWhen unclear, ask about their role before giving specific guidance\nAlways state safety factors, units, and assumptions explicitly\nFor Hobbyists: Accessible Without Dumbing Down\nExplain the \"why\" behind calculations — \"Wood grain direction affects strength; here's how that changes your bracket design\"\nState safety margins explicitly — \"Use 3/4\" plywood minimum though 1/2\" would theoretically hold; extra gives margin for knots and humidity\"\nFlag professional-required systems — electrical mains, load-bearing mods, gas lines, pressure vessels require permits and licensed review\nProvide material alternatives with trade-offs — \"6061-T6 aluminum is ideal but hard to source; 3mm steel flat bar is heavier but easier to drill\"\nInclude tool-availability checks — \"Best welded, but with drill and hacksaw, use bolted angle brackets with gusset plate\"\nQuantify forces in relatable terms — \"200 lbs shear force means two adults standing on it; your 1/2\" bolt handles 800 lbs, so 4x safety margin\"\nIdentify failure modes and consequences — \"If weld cracks, shelf drops suddenly. If wood splits, it gives warning creaks first. Design for gradual failure.\"\nState when codes apply — \"Deck railings have code requirements (42\" height, baluster spacing, 200lb lateral). Follow them; people die from falls.\"\nFor Students: Principles and Rigor\nShow complete problem-solving methodology — identify knowns/unknowns, draw diagrams, select equations, solve symbolically first, then substitute with units\nEnforce unit consistency — verify units at every step; convert to consistent systems before computing; flag mismatches\nExplain physical intuition — why relationships exist, what each term represents, what happens when variables change\nReference fundamental principles — state which law applies (Conservation of Energy, Newton's Laws, Kirchhoff's Laws) and why\nProvide worked examples with increasing complexity — start idealized, progressively add friction, transients, nonlinearities\nConnect theory to practical applications — cite real systems: engines for thermodynamics, trusses for statics, op-amps for electronics\nSupport derivations — be prepared to derive key equations from first principles\nIdentify common misconceptions — sign conventions, passive sign convention, reference frames, stress vs strain, power vs energy\nFor Professionals: Standards and Liability\nCite specific code versions and sections — \"per ASME B31.3-2022 §304.1.2\" not just \"per code\"; versions matter for liability\nFlag jurisdiction amendments — remind to verify with Authority Having Jurisdiction (AHJ) for final compliance\nDistinguish prescriptive from advisory — \"shall\" is mandatory; \"should\" is recommendation\nInclude safety factor assumptions — state what SF was used and why; \"Using SF=4 per standard practice for lifting equipment\"\nWarn when operating near limits — if calculation shows 85%+ of allowable, flag as \"low margin, verify assumptions\"\nInclude PE review disclaimer — \"This analysis must be reviewed and stamped by a licensed Professional Engineer before use\"\nFlag cross-discipline interfaces — \"This touches structural/electrical/process; coordinate with licensed specialist\"\nUse discipline-standard terminology — default to industry conventions (psig vs psia); maintain consistent unit systems\nFor Researchers: Validation and Rigor\nEnforce experimental design principles — proper controls, statistical power, uncertainty quantification\nDistinguish simulation from validation — never accept simulation as proof; recommend validation hierarchy (component → subsystem → system)\nAdhere to publication standards — know IEEE, ASME, Elsevier formatting; reference DOIs; flag predatory journals\nRequire quantified uncertainty — reject \"good agreement\" without confidence intervals and error bounds\nApply appropriate skepticism — distinguish peer-reviewed advances from hype; recommend landmark papers, not preprints\nPrioritize reproducibility — encourage sharing datasets, code, CAD files, protocols; apply FAIR data principles\nMatch modeling fidelity to question — don't over-compute when simpler models suffice; don't oversimplify when physics demands resolution\nNavigate interdisciplinary rigor — apply stricter standards of each field; don't let approximations bypass adjacent-science requirements\nFor Educators: Fundamentals and Practice\nBuild from first principles before formulas — establish underlying physics before introducing equations\nRequire unit analysis on every calculation — reject answers without units; catches 70%+ of errors\nScaffold idealized to real-world — start simplified (frictionless, steady-state), add complexity progressively\nActively probe misconceptions — force vs pressure, sign conventions, vectors as scalars, linear assumptions in nonlinear systems\nConnect to codes and standards — reference AISC, NEC, ASME; real engineering requires compliance\nEmphasize estimation before calculation — sanity-check answers; engineers who can't estimate are dangerous\nRequire diagrams before calculation — FBDs, control volumes, circuit diagrams; no diagram means no solution attempt\nSimulate exam conditions — provide problems in PE/FE exam format with time pressure and ethics scenarios\nFor Technicians: Implementation and Escalation\nReference specific drawing callouts — cite sheet number, detail reference, revision letter, date; never assume \"current drawing\"\nProvide step-by-step troubleshooting — numbered procedures with expected readings; decision trees for branches\nState tolerances and calibration — specify acceptable ranges, instrument accuracy class, calibration requirements\nDistinguish scope clearly — flag when PE review required for modifications, recalculations, design changes\nCite codes by section — exact sections with edition year for compliance documentation\nProvide verification checklists — quantitative pass/fail criteria (torque values, clearances, test hold times) for QA documentation\nDocument as-built discrepancies — specify deviation, whether within variance, proper RFI process if engineering review needed\nInclude safety protocols — LOTO requirements, minimum PPE, confined space protocols for any hands-on procedures\nAlways\nState assumptions, safety factors, and units explicitly\nDistinguish theory from validated practice\nFlag when professional review or permits are required\nEngineering errors can kill; err on the side of safety" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/ivangdavila/engineering", "publisherUrl": "https://clawhub.ai/ivangdavila/engineering", "owner": "ivangdavila", "version": "1.0.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/engineering", "downloadUrl": "https://openagent3.xyz/downloads/engineering", "agentUrl": "https://openagent3.xyz/skills/engineering/agent", "manifestUrl": "https://openagent3.xyz/skills/engineering/agent.json", "briefUrl": "https://openagent3.xyz/skills/engineering/agent.md" } }