duke-leto-test
Test skill to verify ClawHub publishing works correctly.
Why use this skill?
Use the duke-leto-test skill to verify OpenClaw ClawHub connectivity and ensure your agent installation pipeline is working correctly.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/jdrhyne/duke-leto-testWhat This Skill Does
The duke-leto-test skill serves as a fundamental validation mechanism within the OpenClaw ecosystem. Designed specifically to verify the integrity of the ClawHub publishing pipeline, this skill acts as a benchmark for developers and power users to ensure that their local environment and the global repository are communicating effectively. By deploying this skill, you are confirming that the OpenClaw agent can successfully fetch, verify, and initialize external modules without encountering dependency resolution errors or repository access issues. It performs a basic handshake operation that confirms the skill is registered correctly in the ClawHub registry.
Installation
To install this skill, ensure your OpenClaw CLI is updated to the latest version. Open your terminal and execute the following command:
clawhub install openclaw/skills/skills/jdrhyne/duke-leto-test
Once the command finishes, the agent will confirm the installation. You can verify it by running your agent and checking the active skills list to ensure 'duke-leto-test' appears in the manifest.
Use Cases
This skill is primarily used by developers who are currently integrating new custom agents or by those testing the deployment workflow of the OpenClaw platform. It is an essential sanity check for:
- Verifying repository connectivity between the host machine and the OpenClaw cloud.
- Confirming that the environment's security policies permit the installation of third-party community skills.
- Testing automated CI/CD pipelines where OpenClaw agents are deployed across multiple environments.
Example Prompts
- "OpenClaw, please run the duke-leto-test skill to confirm my connection to ClawHub is active."
- "Can you execute the duke-leto-test validation process and report the status of the installation?"
- "Verify that the duke-leto-test skill is properly initialized and ready for production use."
Tips & Limitations
This skill is intended for testing purposes only and contains no functional logic for data processing or system interaction. It is not designed for production workflows and should be uninstalled once you have verified your ClawHub connectivity. If you experience issues during installation, ensure your network settings allow for outbound traffic to the OpenClaw source repository, as firewall configurations are the most common cause of failure for this specific skill.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-jdrhyne-duke-leto-test": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Related Skills
nutrient-openclaw
OpenClaw-native PDF/document processing skill for Nutrient DWS. Best for OpenClaw users who need PDF conversion, OCR, text/table extraction, PII redaction, watermarking, digital signatures, and API credit checks via built-in `nutrient_*` tools. Triggers on OpenClaw tool names (`nutrient_convert_to_pdf`, `nutrient_extract_text`, etc.), "OpenClaw plugin", "Nutrient OpenClaw", and document-processing requests in OpenClaw chats. For non-OpenClaw environments, use the Universal Nutrient Document Processing skill instead.
todo-tracker
Persistent TODO scratch pad for tracking tasks across sessions. Use when user says "add to TODO", "what's on the TODO", "mark X done", "show TODO list", "remove from TODO", or asks about pending tasks. Also triggers on heartbeat to remind about stale items.
sysadmin-toolbox
Tool discovery and shell one-liner reference for sysadmin, DevOps, and security tasks. AUTO-CONSULT this skill when the user is: troubleshooting network issues, debugging processes, analyzing logs, working with SSL/TLS, managing DNS, testing HTTP endpoints, auditing security, working with containers, writing shell scripts, or asks 'what tool should I use for X'. Source: github.com/trimstray/the-book-of-secret-knowledge
munger-observer
Daily wisdom review applying Charlie Munger's mental models to your work and thinking. Use when asked to review decisions, analyze thinking patterns, detect biases, apply mental models, do a "Munger review", or run the Munger Observer. Triggers on scheduled daily reviews or manual requests like "run munger observer", "review my thinking", "check for blind spots", or "apply mental models".
jira
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.