← Back to Skills Marketplace
Portable Tools
by
TunaIssaCoding
· GitHub ↗
· v1.2.0
2693
Downloads
1
Stars
3
Active Installs
6
Versions
Install in OpenClaw
/install portable-tools
Description
Build cross-device tools without hardcoding paths or account names
Usage Guidance
This skill is a portable-tooling guide and is internally consistent, but some examples explicitly ask you to show raw tokens and keychain output as "proof." Before using: (1) do NOT paste raw access tokens or secrets into public chat or logs — redact or hash them (e.g., show first/last 4 chars or a SHA256 of the token) when proving changes; (2) run the pre-publish checklist and debugging commands locally in a safe environment, not in a public/shared session; (3) if an agent or helper asks for BEFORE/AFTER values, prefer deterministic comparisons (hashes) or masked output instead of full secrets; (4) consider adding guidance to SKILL.md that any exported or reported token values must be redacted and that proofs should use non-reversible fingerprints rather than raw tokens.
Capability Analysis
Type: OpenClaw Skill
Name: portable-tools
Version: 1.2.0
The skill bundle provides a methodology and a shell script (`pre-publish-checklist.sh`) to help developers build portable tools. The `SKILL.md` and `README.md` offer guidance and examples of good coding practices. The shell script performs static analysis on a user-specified directory to check for hardcoded paths, input validation, and error handling, which is a benign code quality check. There is no evidence of data exfiltration, malicious execution, persistence, prompt injection against the agent, or obfuscation across any of the files.
Capability Assessment
Purpose & Capability
Name and description match the actual contents: a methodology, examples, and a pre-publish checklist for making shell tools portable. There are no unexpected binaries, environment variables, or unrelated install steps required.
Instruction Scope
SKILL.md and examples explicitly instruct running platform commands (e.g., macOS 'security find-generic-password') and showing BEFORE/AFTER token values. That is coherent for debugging auth portability, but the explicit encouragement to paste raw tokens and access keychain output increases the chance of accidental secrets disclosure. The instructions do not instruct reading unrelated system files or sending data to external endpoints, but they do ask for concrete secret values as 'proof.'
Install Mechanism
Instruction-only skill with no install spec and no downloads. No files are written or arbitrary code fetched during install—lowest-risk install posture.
Credentials
The skill does not declare any required environment variables or credentials (none listed). However, examples/diagnostics reference local credential stores (keychain) and tokens. This is reasonable for an OAuth/tool-portability guide, but users should be aware that following the examples may surface local credentials. The declared requirements are proportionate to the stated purpose.
Persistence & Privilege
The skill is not always-included, does not request persistent system privileges, and contains no install hooks. It does not modify other skills or system-wide settings.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install portable-tools - After installation, invoke the skill by name or use
/portable-tools - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.0
portable-tools v1.2.0
- SKILL.md rewritten for greater clarity and conciseness, emphasizing methodology and actionable patterns.
- Description updated to focus on building cross-device tools without hardcoding paths or account names.
- Redundant details and excessive narrative trimmed to clarify core principles, mandatory patterns, and debugging checklists.
- Anti-patterns and real-world OAuth example made more direct and accessible.
- Resulting documentation now provides a clearer, more universal set of guidelines for portable tool development.
v1.1.1
## portable-tools 1.1.1
- No code or documentation changes; version bump only.
- All methodologies, patterns, and anti-patterns for cross-device tool development remain unchanged.
v1.1.0
portable-tools 1.1.0
- Updated documentation in README.md with more detailed methodology and real-world examples.
- Expanded anti-patterns and debugging steps for building cross-device tools.
- Added pre-flight checklist and explicit testing/documentation recommendations.
- Improved guidance on fallback chains, helpful errors, and validation patterns for tool development.
v1.0.2
## portable-tools 1.0.2 Changelog
- Updated documentation for clarity and structure in methodology and examples.
- Improved and reorganized README to better guide building cross-device portable tools.
- Enhanced step-by-step debugging and pre-flight checklist sections.
- No code or logic changes; documentation only.
v1.0.1
**portable-tools 1.0.1 Changelog**
- Updated documentation in README.md for improved clarity and completeness.
- No functional or code changes; this release focuses solely on enhancing written guidance for cross-device tool development.
- No changes to SKILL.md or core methodology content.
v1.0.0
Initial public release based on OAuth refresher debugging experience.
- Introduces a cross-device development methodology focused on portability and robustness.
- Outlines a three-question checklist for identifying variable configuration, proving correct operation, and handling failure cases.
- Provides mandatory coding patterns: explicit parameters, data validation, fallback chains, and helpful error messages.
- Includes a pre-flight checklist covering discovery, implementation, testing, and documentation phases.
- Features real-world code examples, anti-patterns, and tested solutions for building tools that work reliably across diverse setups.
Metadata
Frequently Asked Questions
What is Portable Tools?
Build cross-device tools without hardcoding paths or account names. It is an AI Agent Skill for Claude Code / OpenClaw, with 2693 downloads so far.
How do I install Portable Tools?
Run "/install portable-tools" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Portable Tools free?
Yes, Portable Tools is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Portable Tools support?
Portable Tools is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Portable Tools?
It is built and maintained by TunaIssaCoding (@tunaissacoding); the current version is v1.2.0.
More Skills