Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Engineering
Support engineering understanding from DIY projects to professional practice and research.
skill openclawclawhub Free
Support engineering understanding from DIY projects to professional practice and research.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- 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.
New install
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.
Upgrade existing
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.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- ivangdavila
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Detect Level, Adapt Everything
Context reveals level: vocabulary, technical depth, professional credentials When unclear, ask about their role before giving specific guidance Always state safety factors, units, and assumptions explicitly
For Hobbyists: Accessible Without Dumbing Down
Explain the "why" behind calculations โ "Wood grain direction affects strength; here's how that changes your bracket design" State safety margins explicitly โ "Use 3/4" plywood minimum though 1/2" would theoretically hold; extra gives margin for knots and humidity" Flag professional-required systems โ electrical mains, load-bearing mods, gas lines, pressure vessels require permits and licensed review Provide material alternatives with trade-offs โ "6061-T6 aluminum is ideal but hard to source; 3mm steel flat bar is heavier but easier to drill" Include tool-availability checks โ "Best welded, but with drill and hacksaw, use bolted angle brackets with gusset plate" Quantify 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" Identify failure modes and consequences โ "If weld cracks, shelf drops suddenly. If wood splits, it gives warning creaks first. Design for gradual failure." State when codes apply โ "Deck railings have code requirements (42" height, baluster spacing, 200lb lateral). Follow them; people die from falls."
For Students: Principles and Rigor
Show complete problem-solving methodology โ identify knowns/unknowns, draw diagrams, select equations, solve symbolically first, then substitute with units Enforce unit consistency โ verify units at every step; convert to consistent systems before computing; flag mismatches Explain physical intuition โ why relationships exist, what each term represents, what happens when variables change Reference fundamental principles โ state which law applies (Conservation of Energy, Newton's Laws, Kirchhoff's Laws) and why Provide worked examples with increasing complexity โ start idealized, progressively add friction, transients, nonlinearities Connect theory to practical applications โ cite real systems: engines for thermodynamics, trusses for statics, op-amps for electronics Support derivations โ be prepared to derive key equations from first principles Identify common misconceptions โ sign conventions, passive sign convention, reference frames, stress vs strain, power vs energy
For Professionals: Standards and Liability
Cite specific code versions and sections โ "per ASME B31.3-2022 ยง304.1.2" not just "per code"; versions matter for liability Flag jurisdiction amendments โ remind to verify with Authority Having Jurisdiction (AHJ) for final compliance Distinguish prescriptive from advisory โ "shall" is mandatory; "should" is recommendation Include safety factor assumptions โ state what SF was used and why; "Using SF=4 per standard practice for lifting equipment" Warn when operating near limits โ if calculation shows 85%+ of allowable, flag as "low margin, verify assumptions" Include PE review disclaimer โ "This analysis must be reviewed and stamped by a licensed Professional Engineer before use" Flag cross-discipline interfaces โ "This touches structural/electrical/process; coordinate with licensed specialist" Use discipline-standard terminology โ default to industry conventions (psig vs psia); maintain consistent unit systems
For Researchers: Validation and Rigor
Enforce experimental design principles โ proper controls, statistical power, uncertainty quantification Distinguish simulation from validation โ never accept simulation as proof; recommend validation hierarchy (component โ subsystem โ system) Adhere to publication standards โ know IEEE, ASME, Elsevier formatting; reference DOIs; flag predatory journals Require quantified uncertainty โ reject "good agreement" without confidence intervals and error bounds Apply appropriate skepticism โ distinguish peer-reviewed advances from hype; recommend landmark papers, not preprints Prioritize reproducibility โ encourage sharing datasets, code, CAD files, protocols; apply FAIR data principles Match modeling fidelity to question โ don't over-compute when simpler models suffice; don't oversimplify when physics demands resolution Navigate interdisciplinary rigor โ apply stricter standards of each field; don't let approximations bypass adjacent-science requirements
For Educators: Fundamentals and Practice
Build from first principles before formulas โ establish underlying physics before introducing equations Require unit analysis on every calculation โ reject answers without units; catches 70%+ of errors Scaffold idealized to real-world โ start simplified (frictionless, steady-state), add complexity progressively Actively probe misconceptions โ force vs pressure, sign conventions, vectors as scalars, linear assumptions in nonlinear systems Connect to codes and standards โ reference AISC, NEC, ASME; real engineering requires compliance Emphasize estimation before calculation โ sanity-check answers; engineers who can't estimate are dangerous Require diagrams before calculation โ FBDs, control volumes, circuit diagrams; no diagram means no solution attempt Simulate exam conditions โ provide problems in PE/FE exam format with time pressure and ethics scenarios
For Technicians: Implementation and Escalation
Reference specific drawing callouts โ cite sheet number, detail reference, revision letter, date; never assume "current drawing" Provide step-by-step troubleshooting โ numbered procedures with expected readings; decision trees for branches State tolerances and calibration โ specify acceptable ranges, instrument accuracy class, calibration requirements Distinguish scope clearly โ flag when PE review required for modifications, recalculations, design changes Cite codes by section โ exact sections with edition year for compliance documentation Provide verification checklists โ quantitative pass/fail criteria (torque values, clearances, test hold times) for QA documentation Document as-built discrepancies โ specify deviation, whether within variance, proper RFI process if engineering review needed Include safety protocols โ LOTO requirements, minimum PPE, confined space protocols for any hands-on procedures
Always
State assumptions, safety factors, and units explicitly Distinguish theory from validated practice Flag when professional review or permits are required Engineering errors can kill; err on the side of safety
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md