Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Enterprise
Navigate enterprise software development with legacy integration, compliance requirements, stakeholder management, and architectural decisions at scale.
skill openclawclawhub Free
Navigate enterprise software development with legacy integration, compliance requirements, stakeholder management, and architectural decisions at scale.
โฌ 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, architecture.md, compliance.md, legacy.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
When to Use
Working in corporate environments where decisions involve legacy systems, formal processes, compliance, multi-team coordination, or architectural trade-offs at scale.
Quick Reference
TopicFileLegacy patternslegacy.mdCompliance rulescompliance.mdArchitecture decisionsarchitecture.md
1. Legacy First Mindset
Assume existing systems until proven otherwise Integration cost > development cost in most decisions "Replace vs wrap" analysis before any architecture change Document all integration points touched
2. Stakeholder Mapping
RoleCares AboutLanguageEngineeringTechnical debt, velocityPatterns, trade-offsProductFeatures, timelineUser impact, scopeSecurityRisk, complianceThreat models, controlsFinanceCost, ROITCO, licensingLegalLiability, dataContracts, GDPR Translate technical decisions into each stakeholder's language.
3. Change Management
No breaking changes without migration path Feature flags before hard switches Rollback plan for every deployment Document blast radius of failures
4. Compliance Awareness
PCI, SOC2, HIPAA, GDPR implications in every data decision Audit trail requirements โ logging design Data residency affects architecture Ask: "Who audits this? What do they need?"
5. Documentation as Deliverable
Enterprise code without docs = technical debt. ADRs (Architecture Decision Records) for major choices Runbooks for operations API contracts before implementation Dependency graphs updated with changes
6. Security by Default
Principle of least privilege in all designs Secrets in vault, never in code or config files Network segmentation assumptions Zero trust between services
7. Observability Investment
Logging, metrics, tracing from day one Correlation IDs across service boundaries SLI/SLO definitions before launch Alert fatigue is a system design failure
Enterprise Traps
Assuming greenfield when there's always legacy โ scope explosion Optimizing for developer experience over ops burden โ 3am pages Skipping security review for "internal tools" โ breach vector Building before buying โ reinventing solved problems Over-abstracting early โ framework nobody understands Under-documenting decisions โ knowledge silos
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
4 Docs
- SKILL.md
- architecture.md
- compliance.md
- legacy.md