Agent skill
import-github-dirs
Import specific directories from external GitHub repos without cloning. Uses tarball extraction to pull only what you need. TRIGGER when user wants to copy files/folders from another repo.
Install this agent skill to your Project
npx add-skill https://github.com/iamhenry/ai-project-starter-kit/tree/main/.opencode/skills/import-github-dirs
SKILL.md
Import GitHub Directories
TRIGGER CONDITIONS
USE when:
- "bring in files from [repo]"
- "import directories from GitHub"
- Copying code from external repos
SKIP when:
- User wants to clone entire repo
- Just need single file (use raw URL instead)
One-Command Import
curl -L https://github.com/{owner}/{repo}/tarball/{branch} | \
tar -xz --strip-components=1 --wildcards '*/{dir1}/*' '*/{dir2}/*'
Examples
Single directory:
curl -L https://github.com/rjs/shaping-skills/tarball/main | \
tar -xz --strip-components=1 --wildcards '*/shaping/*'
Multiple directories:
curl -L https://github.com/rjs/shaping-skills/tarball/main | \
tar -xz --strip-components=1 --wildcards '*/breadboarding/*' '*/shaping/*'
How It Works
- HTTP download of tarball (no git operations)
--strip-components=1removes root folder--wildcardsextracts only matching paths- Files land in current directory, ready to move/stage/commit
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
iamhenry/ai-project-starter-kit
verification-gate
Reusable verification gate for completed work before commit or merge. Use when implementation is done and Claude must prove the task works, verify the main user flow, choose between browser-flow, browser-static, or non-browser validation, and return a PASS/FAIL/BLOCKED verdict with evidence. When browser verification is needed, rely on the agent-browser skill for browser actions, screenshots, and recordings.
iamhenry/ai-project-starter-kit
osgrep
Semantic code search using natural language queries. Use when users ask "where is X implemented", "how does Y work", "find the logic for Z", or need to locate code by concept rather than exact text. Returns file paths with line numbers and code snippets.
iamhenry/ai-project-starter-kit
napkin
Maintain a per-repo napkin file that tracks mistakes, corrections, and what works. Activates EVERY session, unconditionally. Read the napkin before doing anything. Write to it continuously as you work — not just at session boundaries. Log your own mistakes, not just user corrections. The napkin lives in the repo at `.opencode/napkin.md`.
iamhenry/ai-project-starter-kit
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
iamhenry/ai-project-starter-kit
tmux
Manage concurrent background processes using tmux. Use when spawning dev servers, running long-running tasks, monitoring multiple processes, or capturing output from background commands without blocking the main session.
iamhenry/ai-project-starter-kit
viral-research
Viral content research and DNA extraction for Instagram Reels. Use this skill whenever you need to research what's performing in a niche on Instagram, find viral faceless Reels, download and analyze them frame-by-frame, identify patterns, and produce a structured research brief. Trigger whenever the user mentions viral content research, Instagram research, Reel analysis, content DNA, swipe file building, niche research, competitor analysis for social content, or wants to understand why certain content performs. Also trigger when the user wants to find content formats to adapt, study what's working in a niche, or build a research-backed content strategy. This skill is research-only — it does not generate or publish content.
Didn't find tool you were looking for?