remote-skill-engineCache and use skills from ClawHub and GitHub as if locally installed. Stores remote skills in local cache folder for offline use.
Install via ClawdBot CLI:
clawdbot install oki3505f/remote-skill-engineGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://clawhub.com/api/skills/search?q=<queryUses known external API (expected, informational)
api.github.comAudited Apr 16, 2026 · audit v1.0
Generated Mar 20, 2026
A security operations team needs to quickly find and test multiple vulnerability scanning skills from ClawHub and GitHub repositories. They use the search functionality to discover relevant skills, cache them locally for offline analysis, and compare features before selecting the most appropriate tool for their environment.
A software development team wants to enhance their CI/CD pipeline with code review and testing skills. They batch cache multiple coding-related skills from GitHub repositories, sync them regularly for updates, and use them locally without internet dependency during pipeline execution in isolated environments.
Academic researchers need to evaluate multiple data analysis and visualization skills for a research project. They fetch metadata from various sources, compare capabilities using the comparison script, cache selected skills for offline use in labs with restricted internet access, and maintain synchronized versions across team members.
An IT department needs to standardize automation skills across multiple teams. They create a JSON list of approved skills, batch cache them to ensure consistent versions, configure auto-sync for updates, and provide offline access for field technicians working in locations with unreliable internet connectivity.
A consulting firm maintains a portfolio of specialized skills for different client engagements. They regularly search for new skills across registries, cache promising candidates for evaluation, compare them against existing tools, and maintain synchronized cached versions that consultants can use offline at client sites.
Offer premium access to ClawHub registry with advanced search filters, verified skill ratings, and priority caching capabilities. Revenue comes from subscription fees for organizations needing curated, high-quality skill collections with reliability guarantees and enterprise support.
Provide enterprise-grade cache management solutions with centralized control, compliance reporting, and automated skill vetting processes. Revenue is generated through licensing fees for management consoles that offer team collaboration features, audit trails, and integration with existing IT infrastructure.
Create a marketplace where developers can publish and monetize skills. Revenue comes from transaction fees on skill sales, featured listings for premium placement in search results, and certification services that verify skill quality and security for enterprise customers.
💬 Integration Tip
Integrate with existing CI/CD pipelines by adding cache update scripts to build processes, ensuring skills remain current without manual intervention while maintaining offline availability for deployment environments.
Scored Jun 17, 2026
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Essential Git commands and workflows for version control, branching, and collaboration.
GitHub API integration with managed OAuth. Access repositories, issues, pull requests, commits, branches, and users. Use this skill when users want to interact with GitHub repositories, manage issues and PRs, search code, or automate workflows. For other third party apps, use the api-gateway skill (
Advanced git operations beyond add/commit/push. Use when rebasing, bisecting bugs, using worktrees for parallel development, recovering with reflog, managing subtrees/submodules, resolving merge conflicts, cherry-picking across branches, or working with monorepos.
Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.
Query the DeepWiki MCP server for GitHub repository documentation, wiki structure, and AI-powered questions.