| name | native-tools |
| description | GitHub CLI, docker commands, git operations, curl, native CLI tools, gh issue, gh pr, container, repository, API calls (project) |
Native Tools Skill
Use native CLI tools directly instead of building custom integrations. Claude Code has full terminal access - use it.
Quick Start
PCP follows the native-first principle: if a CLI tool exists, use it directly. Don't build wrapper scripts.
Available CLI tools:
gh - GitHub CLI (issues, PRs, repos)
docker - Container management
git - Version control
curl - HTTP/API calls
- Standard Unix tools (grep, find, ls, etc.)
Native-First Principle
Rule: Only build custom scripts for things that require:
- OAuth complexity (Microsoft Graph)
- Structured data schema (knowledge base, vault)
- NLP extraction (entity detection)
Everything else? Use the CLI directly.
GitHub CLI (gh)
Issues
gh issue create --repo owner/repo --title "Bug: login fails" --body "Description here"
gh issue list --assignee @me
gh issue list --repo owner/repo --state open
gh issue view 123 --repo owner/repo
gh issue close 123 --repo owner/repo
gh issue comment 123 --body "Fixed in PR #456"
Pull Requests
gh pr create --title "Fix login bug" --body "Fixes #123"
gh pr list --author @me
gh pr list --state open
gh pr view 456
gh pr review 456 --approve
gh pr review 456 --request-changes --body "Please fix X"
gh pr merge 456 --squash
Other gh Commands
gh search code "function_name" --repo owner/repo
gh repo view owner/repo
gh repo clone owner/repo
gh release list --repo owner/repo
gh release create v1.0.0 --generate-notes
Docker
Container Management
docker ps
docker ps -a
docker logs container_name
docker logs -f container_name
docker exec container_name command
docker exec -it container_name bash
docker stats container_name
docker inspect container_name
Compose Operations
docker compose up -d
docker compose down
docker compose up -d --build
docker compose logs -f service_name
Images
docker images
docker pull image:tag
docker build -t name:tag .
Git
Status and History
git status
git log --oneline -10
git log --oneline --all --graph
git diff
git diff --staged
git diff branch1..branch2
Branching
git checkout -b feature/new-thing
git checkout main
git branch -a
Commits and Push
git add .
git commit -m "feat: add new feature"
git push origin branch-name
git push -u origin branch-name
Stash
git stash
git stash pop
git stash list
HTTP/API Calls (curl)
Basic Requests
curl -s https://api.example.com/endpoint | jq .
curl -s -X POST https://api.example.com/endpoint \
-H "Content-Type: application/json" \
-d '{"key": "value"}' | jq .
curl -s -H "Authorization: Bearer $TOKEN" \
https://api.example.com/protected | jq .
Common Patterns
curl -s https://api.example.com/health | jq .
curl -L -o filename.zip https://example.com/file.zip
curl -L https://example.com/redirect
When the User Says...
| User Request | Command |
|---|
| "Create a GitHub issue for X" | gh issue create --title "X" --body "..." |
| "What PRs need review?" | gh pr list --state open |
| "What containers are running?" | docker ps |
| "Show me the logs for X" | docker logs X |
| "What's the git status?" | git status |
| "Commit these changes" | git add . && git commit -m "..." |
| "Call this API endpoint" | curl -s URL | jq . |
| "What's the latest release?" | gh release list --repo owner/repo |
What NOT to Build Custom Scripts For
| Need | Use This | NOT This |
|---|
| GitHub issues | gh issue create | custom GitHub API script |
| Container logs | docker logs | custom Docker API script |
| Git operations | git commands | custom git wrapper |
| API testing | curl | custom HTTP client |
| File search | find, grep | custom file finder |
What TO Build Custom Scripts For
| Need | Why Custom? | Script |
|---|
| Microsoft Graph | OAuth token management | microsoft_graph.py |
| Knowledge base | Structured schema + search | knowledge.py |
| Entity extraction | NLP with Claude | vault_v2.py |
| Email processing | OAuth + structured storage | email_processor.py |
Tips
- Always check if a CLI tool exists first - Most common operations have excellent CLI tools
- Use
jq for JSON output - Pipe API responses through jq . for formatting
- Use
-s (silent) with curl - Hides progress bars for cleaner output
- Use
--help - Every CLI tool has help: gh issue --help, docker --help
- Combine with PCP - Use CLI tools then capture results to vault if needed
Related Skills
- pcp-operations - For PCP-specific functions
- vault-operations - For capturing CLI outputs to vault
- knowledge-base - For storing permanent facts from CLI exploration