takazudo/gcoc-research
skills/gcoc-research/SKILL.md
Web research using GitHub Copilot CLI cheap mode — same as /gco-research but forces the free gpt-4.1 model. Use when: (1) User says 'gcoc research' or 'copilot cheap research', (2) Premium quota is exhausted, (3) Research topic is simple and doesn't need opus reasoning.
$ install --global
skillsauthnpx skillsauth add takazudo/claude-resources gcoc-researchInstall 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:28 AM125.0s1 file scanned
SKILL.md
- name:
- gcoc-research
- description:
- Web research using GitHub Copilot CLI cheap mode — same as /gco-research but forces the free gpt-4.1 model. Use when: (1) User says 'gcoc research' or 'copilot cheap research', (2) Premium quota is exhausted, (3) Research topic is simple and doesn't need opus reasoning.
GCOC Research (Cheap)
Same behavior as /gco-research — web research synthesized by Claude Code — but forces gpt-4.1 from the start. No Premium Requests consumed.
How It Differs from /gco-research
- Model:
gpt-4.1(forced viaGCO_MODEL=gpt-4.1) - Skip the
GCO_USED_FALLBACK=stderr check — it's the user's deliberate choice, not a fallback
Process
Follow the exact same process as /gco-research.
Step 1: Understand the Research Topic
Clarify what needs to be researched — specific question, scope, how findings will be used.
Step 2: Build Research Prompt
Same research prompt as /gco-research (topic, specific questions, request for findings with sources/URLs, alternatives, recommendations, code examples).
Step 3: Run Copilot with forced cheap model
LOGDIR=$(node $HOME/.claude/scripts/get-logdir.js)
mkdir -p "$LOGDIR"
DATETIME=$(date +%Y%m%d_%H%M%S)
SLUG="<short-topic-slug>"
GCO_MODEL=gpt-4.1 \
bash $HOME/.claude/skills/gco/scripts/gco-run.sh \
"<research prompt>" \
"$LOGDIR/${DATETIME}-gcoc-research-${SLUG}.md" \
"$LOGDIR/${DATETIME}-gcoc-research-${SLUG}-stderr.log"
Timeout: 15 minutes.
Step 4: Collect Results
- Read the output file
- If empty or missing, check stderr log for errors
- If Copilot timed out or failed, jump to Fallback
- Do NOT check for
GCO_USED_FALLBACK=marker — the cheap model is intentional
Step 5: Fallback
Same as /gco-research — if Copilot timed out, produced no output, or is not installed, spawn a researcher subagent.
Step 6: Synthesize
Organize findings, verify key claims where possible, present with source references.
Step 7: Save Research Log
node $HOME/.claude/scripts/save-file.js "{logdir}/{timestamp}-research-{topic}.md" "<content>"
pnpm dlx @takazudo/mdx-formatter --write <file>
Important Notes
- Copilot does native web research — no need to paste content into the prompt
- All file writing done by Claude Code, never by Copilot
gpt-4.1has zero Premium multiplier on the Pro plan — safe to use when quota is tight- NEVER use
~in paths — use$HOME
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