takazudo/subagent-tweaker
skills/subagent-tweaker/SKILL.md
Fix, improve, or update existing Claude Code custom agents (subagents). Use when: (1) User reports an agent isn't working well, (2) User wants to adjust agent behavior, tools, or model, (3) User says 'fix agent', 'update agent', 'tweak agent', 'agent not working'. Edits agent frontmatter, tool restrictions, prompts.
$ install --global
skillsauthnpx skillsauth add takazudo/claude-resources subagent-tweakerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 8, 2026, 4:34 AM194.4s1 file scanned
SKILL.md
- name:
- subagent-tweaker
- description:
- Fix, improve, or update existing Claude Code custom agents (subagents). Use when: (1) User reports an agent isn't working well, (2) User wants to adjust agent behavior, tools, or model, (3) User says 'fix agent', 'update agent', 'tweak agent', 'agent not working'. Edits agent frontmatter, tool restrictions, prompts.
Tweak Custom Agent
Workflow
Step 1: Identify the agent
Find agents at:
$HOME/.claude/agents/*.md(personal).claude/agents/*.md(project)
Read the agent file to understand current configuration.
Step 2: Diagnose the issue
Common problems and fixes:
| Problem | Likely Cause | Fix |
|---------|-------------|-----|
| Agent not being used | Poor description | Rewrite with clear trigger keywords |
| Agent too slow | Wrong model | Switch to sonnet or haiku |
| Agent can't edit files | tools missing Write/Edit | Add needed tools to allowlist |
| Agent doing too much | No tool restrictions | Add tools: or disallowedTools: |
| Agent forgets context | No persistent memory | Add memory: user or memory: project |
| Agent runs too long | No turn limit | Add maxTurns: N |
Step 3: Apply changes
Edit the agent's Markdown file. Preserve existing content that works well.
Frontmatter fields reference:
| Field | Description |
|-------|-------------|
| name | Identifier (lowercase, hyphens) |
| description | When to use (Claude reads this for delegation) |
| model | opus, sonnet, haiku, inherit |
| tools | Tool allowlist (inherits all if omitted) |
| disallowedTools | Tool denylist |
| permissionMode | default, acceptEdits, delegate, dontAsk, bypassPermissions, plan |
| maxTurns | Max agentic turns |
| skills | Preloaded skills |
| mcpServers | Available MCP servers |
| hooks | Scoped lifecycle hooks |
| memory | user, project, local |
Step 4: Format the agent file
Format the edited agent file using the mdx-formatter to ensure consistent markdown formatting:
pnpm dlx @takazudo/mdx-formatter --write <path-to-agent-file.md>
Step 5: Verify
After editing:
- Confirm YAML frontmatter has no syntax errors
- Check tool restrictions match intended behavior
- Verify description contains keywords users would say
Tips
- Keep agent body (system prompt) focused and concise
- Subagents cannot nest - don't add
Tasktool to agents that will be spawned as subagents - When adjusting tools, prefer
disallowedToolsovertoolsif only blocking a few descriptionis the primary trigger mechanism - this is the most impactful field to improve
Related Skills
takazudo/finalize-codex-work
tools
VerifiedTrustedCommunity
Acceptance gate for a branch produced by an OpenAI Codex CLI run — usually Codex implementing a /big-plan epic that was handed off to it. Codex reports the work 'done' (or the user flags it WIP with corrections); this skill confirms the branch actually fulfils the original spec, fixes what falls short, and routes larger discoveries into GitHub issues. Use when: (1) User says '/finalize-codex-work', 'finalize codex work', 'confirm the codex work', 'check the codex branch', or 'codex said it's done', (2) A branch is the result of a Codex CLI session and needs verification against its spec issue/PR, (3) After assigning a /big-plan epic to Codex CLI. Pass -m/--merge to run /pr-complete -c at the end.
11SKILL.mdUpdated Jul 10, 2026
takazudo/fig-url-refer
tools
VerifiedTrustedCommunity
Read a Figma design node directly from a share URL via the Figma REST API — no Dev Mode subscription, no MCP, no desktop app. Renders the node to PNG and dumps its full style/layout JSON so the design can be described, compared, or implemented. Use whenever the user gives a Figma design URL (figma.com/design/... or /file/...) and wants to see, read, inspect, reference, or implement that node — including `/fig-url-refer <url>`. This is the URL-based counterpart to `/figrefer` (which needs a Dev-plan desktop MCP); prefer this one when the input is a URL rather than a live desktop selection.
11SKILL.mdUpdated Jul 10, 2026
takazudo/dev-codex-sync-settings-from-claude
tools
VerifiedTrustedCommunity
Sync the user's Claude Code workflow skills into the OpenAI Codex CLI settings repo ($HOME/.codex) as Codex-native ports, fix the Codex .gitignore for new local state, then commit and push. Use when: (1) user says '/dev-codex-sync-settings-from-claude', 'sync codex settings', 'sync claude skills to codex', 'port skills to codex', or 'update codex from claude'; (2) after updating ~/.claude workflow skills (big-plan, x, x-as-pr, x-wt-teams) and Codex should catch up; (3) the $HOME/.codex repo has drifted behind $HOME/.claude. The ports are condensed Codex-native REWRITES, never file copies.
11SKILL.mdUpdated Jul 10, 2026
takazudo/video-reader
development
VerifiedTrustedCommunity
Analyze a video file (mov, mp4, webm, etc.) or a YouTube video by extracting still frames with ffmpeg and reading them chronologically with vision — Claude cannot ingest video files directly. Use whenever the user provides a video file path or YouTube URL and wants to know what happens in it: "read this video", "watch this video", "check this recording", "what happens in this .mov/.mp4", analyzing a screen recording of a UI bug, or verifying UI behavior captured in a video, even if they don't name this skill.
11SKILL.mdUpdated Jul 7, 2026