Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Deploydevnlu
Deploys the application to the SupplyWhy development EC2 server via SSH, updates image tag if provided, applies Kubernetes deployment, and verifies rollout s...
skill openclawclawhub Free
Deploys the application to the SupplyWhy development EC2 server via SSH, updates image tag if provided, applies Kubernetes deployment, and verifies rollout s...
โฌ 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, _meta.json, index.js, skill.json
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.4
Provenance
- Publisher
- yusong-7456
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
DeployDevNLU
Deploy the application to SupplyWhy via Slack natural language commands.
Instructions
Execute the following steps in order. Verify each step succeeds before proceeding to the next.
Step 1: Add SSH Key to Agent
Run the following command to add the SSH key: ssh-add ~/.ssh/supplywhy-dev-key.pem Verification: The command should output Identity added: ~/.ssh/supplywhy-dev-key.pem or similar. If you see "Could not open a connection to your authentication agent", the ssh-agent may not be running. If you see "No such file or directory", the key file is missing. Stop and report to user if: The key cannot be added.
Step 2: Test SSH Connection
Before deploying, verify the SSH connection works: ssh supplywhy-dev-master "echo 'SSH connection successful'" Verification: Should output SSH connection successful. If you see connection timeout, permission denied, or host not found errors, the SSH connection is not working. Stop and report to user if: SSH connection fails.
Step 3: Update Image Tag
If an IMAGE_TAG argument was provided ($ARGUMENTS), update the deployment.yaml with the new tag: ssh supplywhy-dev-master "sed -i 's|590183820143.dkr.ecr.us-west-2.amazonaws.com/genie:.*|590183820143.dkr.ecr.us-west-2.amazonaws.com/genie:$ARGUMENTS|' genie/deployment.yaml" Verification: Run a quick check to confirm the tag was updated: ssh supplywhy-dev-master "grep 'image:' genie/deployment.yaml" The output should show the new tag you provided. Skip this step if: No IMAGE_TAG argument was provided (deploy with existing tag). Stop and report to user if: The sed command fails.
Step 4: Deploy via kubectl
SSH into the EC2 server and run the kubectl deployment command: ssh supplywhy-dev-master "cd genie && kubectl apply -f deployment.yaml" Verification: The kubectl output should show resources being created, configured, or unchanged. Look for lines like: deployment.apps/xxx configured service/xxx unchanged Stop and report to user if: kubectl returns errors (e.g., "error: the path does not exist", "connection refused") Any resource shows error status
Step 5: Verify Deployment Status
After applying, check that the deployment is rolling out successfully: ssh supplywhy-dev-master "kubectl rollout status deployment -n default --timeout=60s" Verification: Should show successfully rolled out for deployments. If it times out or shows errors, the deployment may have issues. Report to user: The final status of all deployments, whether successful or failed.
Success Criteria
The deployment is successful when: SSH key was added successfully SSH connection to server works Image tag was updated (if argument provided) kubectl apply completed without errors Deployment rollout status shows success
Troubleshooting
If the deployment fails at any step: SSH key issues: Verify the key exists at ~/.ssh/supplywhy-dev-key.pem and has correct permissions (600) SSH connection issues: Check network access and that your IP is allowed in security groups kubectl apply errors: Verify deployment.yaml exists in the genie folder on the server Rollout failures: Check pod logs with kubectl logs or describe the deployment with kubectl describe deployment
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
2 Config1 Docs1 Scripts
- SKILL.md
- index.js
- _meta.json
- skill.json