Perplexity Web Search
davila7/claude-code-templates
Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.
Captures human source verification for tracks, timestamps it, and updates track files.
Install Verify Sources
$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill verify-sources -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bitwize-music-studio/claude-ai-music-skills verify-sources --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/verify-sources .claude/skills/verify-sources && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "verify-sources" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/verify-sources into .claude/skills/verify-sources/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-sources", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/verify-sourcesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill verify-sources -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bitwize-music-studio/claude-ai-music-skills verify-sources --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/verify-sources .agents/skills/verify-sources && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verify-sources" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/verify-sources into .agents/skills/verify-sources/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-sources", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill verify-sources -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bitwize-music-studio/claude-ai-music-skills verify-sources --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/verify-sources .cursor/skills/verify-sources && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "verify-sources" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/verify-sources into .cursor/skills/verify-sources/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-sources", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/bitwize-music-studio/claude-ai-music-skills.git --path skills/verify-sources--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill verify-sources -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bitwize-music-studio/claude-ai-music-skills verify-sources --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/verify-sources .gemini/skills/verify-sources && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "verify-sources" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/verify-sources into .gemini/skills/verify-sources/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-sources", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install bitwize-music-studio/claude-ai-music-skills verify-sourcesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill verify-sources -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/verify-sources .github/skills/verify-sources && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "verify-sources" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/verify-sources into .github/skills/verify-sources/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-sources", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill verify-sources -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bitwize-music-studio/claude-ai-music-skills verify-sources --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/verify-sources .opencode/skills/verify-sources && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "verify-sources" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/verify-sources into .opencode/skills/verify-sources/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-sources", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
verify-sources- GitHub stars
- 540
- Token cost
- ~1.3k tokens
- SKILL.md length
- 508 words
- Files
- 1
- Skills in repo
- 51
- Repo updated
- First seen
- Licence
- CC0-1.0
At a glance
Captures human source verification for tracks, timestamps it, and updates track files.
- Works in 5 steps: Find the Album → Identify Pending Tracks → Walk Through Each Track → …
- Sources need human review before generation
- SKILL.md covers Your Task, Step 1: Find the Album, Step 2: Identify Pending Tracks and Step 3: Walk Through Each Track, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Verify Sources is an agent skill from bitwize-music-studio/claude-ai-music-skills. Captures human source verification for tracks, timestamps it, and updates track files. Use when sources need human review before generation.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Fact-checking and source verification. The repository describes itself as: Human + AI music production workflow for Suno - skills, templates, and tools. The licence is CC0-1.0.
When your agent uses it
- Sources need human review before generation
- Tasks that involve Fact-checking and source verification
Example prompts
- “Use the verify-sources skill to capture human source verification for tracks, timestamps it, and updates track files”
- “/verify-sources”
Requirements
- Pre-approved tools (allowed-tools): Read, Edit, Glob, Grep, Bash, bitwize-music-mcp
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 58f32c2. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadEditGlobGrepBashbitwize-music-mcp
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Verify Sources loads about 1.3k tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 508 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Edit, Glob, Grep, Bash, bitwize-music-mcp
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from bitwize-music-studio/claude-ai-music-skills at commit 58f32c2, republished under its CC0-1.0 licence (© bitwize-music-studio). 508 words, ~1,329 tokens.
Download SKILL.mdSave it as
.claude/skills/verify-sources/SKILL.md (or your agent's skills folder).- name
- verify-sources
- description
- Captures human source verification for tracks, timestamps it, and updates track files. Use when sources need human review before generation.
- allowed-tools
- Read, Edit, Glob, Grep, Bash, bitwize-music-mcp
- argument-hint
- <album-name>
- model
- sonnet
- effort
- low
Your Task
Input: $ARGUMENTS (album name)
Guide the user through source verification for all tracks with pending sources in the specified album.
Source Verification Skill
You facilitate the human source verification gate — the critical checkpoint between research and generation. No track should be generated on Suno until a human has verified that all sources are real, accessible, and accurately represented.
Step 1: Find the Album
- Call
find_album(name)— fuzzy match by name, slug, or partial - If not found, MCP returns available albums
Step 2: Identify Pending Tracks
- Call
get_pending_verifications(album_slug="{album}")— returns pending tracks for the target album - If no album specified, call
get_pending_verifications()for all albums
If no pending tracks:
All tracks in [album] have been verified. No action needed.If pending tracks exist, list them:
SOURCE VERIFICATION: [Album Title]
===================================
Tracks needing verification:
1. [track-slug] — [track-title]
2. [track-slug] — [track-title]
...
Total: X tracks pending verificationStep 3: Walk Through Each Track
For each pending track:
- Call
extract_links(album_slug, track_slug)— extracts markdown links from the track file - Call
extract_links(album_slug, "SOURCES.md")— get the full citation list - Read RESEARCH.md (if it exists) for evidence chains, confidence levels, and claim-to-source mappings — this gives the human verifier context for what each source is supposed to support, not just the URL
- Present sources to the user:
TRACK: [track-title]
--------------------
Sources referenced in this track:
1. [Source Name](URL) — [brief description of what it supports]
2. [Source Name](URL) — [brief description]
...
Please verify:
- Each URL is accessible and contains the claimed information
- No sources are fabricated or hallucinated
- Claims in lyrics are supported by cited sources
Type "verified" to confirm, or describe any issues.- Wait for user response:
- If "verified" (or equivalent affirmative) → update the track
- If issues reported → note them, ask user how to proceed
Step 4: Update Track Files
When user confirms verification for a track:
Call
update_track_field(album_slug, track_slug, "sources-verified", "✅ Verified (YYYY-MM-DD)")— updates the field and auto-rebuilds state cache- Use today's date
Confirm the update:
✅ [track-title] — Sources verified (2025-02-06)- Move to next pending track
Show full SKILL.md (260 more words)Show less
Step 5: Update Album Status (Auto-Advance)
After processing all tracks, check if the album status should advance:
Call
get_album_progress(album_slug)— check how many tracks are now verifiedIf ALL tracks are verified (no more pending):
- Read the album README to check current album status
- If album status is
Research Complete:- Update album README: change
| **Status** | Research Complete |→| **Status** | Sources Verified | - Report: "Album status advanced: Research Complete → Sources Verified"
- Update album README: change
- If album status is
In Progress:- Report: "All track sources verified. Album status stays In Progress (already past research phase)."
If some tracks still pending:
- Report how many remain and which ones
Rebuild state cache: Call
rebuild_state()to ensure MCP server has fresh dataSummary report:
VERIFICATION COMPLETE
=====================
Album: [title]
Tracks verified: X/Y
Album status: [previous] → [new status]
Date: YYYY-MM-DD
All sources verified. This album is cleared for lyric writing.
Next step: /bitwize-music:lyric-writer [track] (write lyrics from verified sources)Partial verification report (if some tracks still pending):
VERIFICATION PROGRESS
=====================
Album: [title]
Tracks verified this session: X
Tracks still pending: Y
- [track-slug] — [reason if known]
Album status: unchanged ([current])
Resume verification later with /bitwize-music:verify-sources [album]Handling Issues
If the user reports a problem with a source:
- Document the issue in the track file as a comment or note
- Do NOT mark as verified — keep status as Pending
- Suggest resolution:
- Source URL broken → "Can you find an updated URL?"
- Source doesn't support claim → "Should we revise the lyric, or find a supporting source?"
- Source is fabricated → "I'll remove this source. Do we need to revise the track?"
- After resolution, re-present for verification
Remember
- Never auto-verify — this skill exists specifically for human review
- Present sources clearly — the user needs to actually check each URL
- Date-stamp everything — verification dates matter for audit trail
- One track at a time — don't rush through, each track matters
- Update state cache — after changes, run indexer update so MCP server has fresh data
© bitwize-music-studio, CC0-1.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/verify-sources of bitwize-music-studio/claude-ai-music-skills.
Open the folder on GitHubat commit 58f32c2
Compare with similar skills
Verify Sources next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Verify Sources this skillbitwize-music-studio/claude-ai-music-skills | 540 | — | ~1.3k | Automated safety check: Notes | CC0-1.0 | |
| Perplexity Web Searchdavila7/claude-code-templates | 32k | 11 repos | ~3.5k | Automated safety check: Notes | MIT | |
| Citation Verification GuideGalaxy-Dawn/claude-scholar | 5.7k | 2 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Article Fact Checkerdigoal/blog | 8.6k | — | ~939 | Automated safety check: Pass | GPL-2.0 | |
| Deep Research Agent TeamImbad0202/academic-research-skills | 51k | — | ~13k | Automated safety check: Pass | Custom licence | |
| Docs Grounding Verifiermicrosoft/apm | 4k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Citation Verification Guide
Galaxy-Dawn/claude-scholar
Reference guidance for checking every citation in academic writing against canonical sources such as DOI, arXiv, CrossRef and Semantic Scholar, to catch fake or wrong references.
Article Fact Checker
digoal/blog
三层审查模型,逐段逐句验证文章真伪、证据链与逻辑结构。Use when the user asks to fact-check, verify, audit, or evaluate the credibility of an article, essay, report, opinion piece, social-media post, or any written claim —…
Deep Research Agent Team
Imbad0202/academic-research-skills
Runs a 13-agent pipeline for rigorous academic research, from forming the question through systematic search, synthesis, bias checks and an APA 7.0 report.
- Official
Docs Grounding Verifier
microsoft/apm
A skill your agent uses to verify CLAIM-LEVEL grounding of a documentation page (or set of pages) against the source code.
Fact Checking
bradygaster/squad
Review and validate claims using counter-hypothesis testing.
More from bitwize-music-studio/claude-ai-music-skills
All 51 skills in this repoAlbum Conceptualizer
bitwize-music-studio/claude-ai-music-skills
Designs album concepts, tracklist architecture, and thematic planning through 7 structured phases.
Album Dashboard
bitwize-music-studio/claude-ai-music-skills
Shows a structured progress dashboard for an album with percentage complete per phase, blocking items, and status breakdown.
Album Ideas
bitwize-music-studio/claude-ai-music-skills
Tracks and manages album ideas including brainstorming, planning, and status updates.
Clipboard
bitwize-music-studio/claude-ai-music-skills
Copies track content (lyrics, style prompts, streaming lyrics) to the system clipboard.
Cloud Uploader
bitwize-music-studio/claude-ai-music-skills
Uploads promo videos and content to Cloudflare R2 or AWS S3.
Configure
bitwize-music-studio/claude-ai-music-skills
Sets up or edits the plugin configuration file interactively.
Related
Categories
Questions about Verify Sources
What does Verify Sources do?
Captures human source verification for tracks, timestamps it, and updates track files. Verify Sources is an agent skill from bitwize-music-studio/claude-ai-music-skills. Captures human source verification for tracks, timestamps it, and updates track files.
When should I use Verify Sources?
Verify Sources fits situations like: sources need human review before generation; tasks that involve Fact-checking and source verification.
How do I install Verify Sources in Claude Code?
Run `npx skills add bitwize-music-studio/claude-ai-music-skills --skill verify-sources -a claude-code`. Or copy the skill folder (skills/verify-sources in bitwize-music-studio/claude-ai-music-skills) into .claude/skills/verify-sources in your project. Claude Code loads it when a task matches its description.
How do I install Verify Sources in Codex?
Run `npx skills add bitwize-music-studio/claude-ai-music-skills --skill verify-sources -a codex`. Or copy the skill folder (skills/verify-sources in bitwize-music-studio/claude-ai-music-skills) into .agents/skills/verify-sources in your project. Codex loads it when a task matches its description.
Can I use Verify Sources in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bitwize-music-studio/claude-ai-music-skills --skill verify-sources -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify-sources, .gemini/skills/verify-sources, .github/skills/verify-sources and .opencode/skills/verify-sources in your project.
What does Verify Sources need to run?
SKILL.md names no scripts, command-line tools or credentials: Verify Sources is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Edit, Glob, Grep, Bash, bitwize-music-mcp.
Does Verify Sources access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Verify Sources safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Verify Sources use?
Verify Sources is published under the CC0-1.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Verify Sources use?
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Verify Sources?
Skills that share tags, products or a category with Verify Sources: Perplexity Web Search (davila7/claude-code-templates, 32k stars), Citation Verification Guide (Galaxy-Dawn/claude-scholar, 5.7k stars), Article Fact Checker (digoal/blog, 8.6k stars) and Deep Research Agent Team (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Verify Sources?
bitwize-music-studio (a GitHub organization) maintains it in bitwize-music-studio/claude-ai-music-skills, which has 540 GitHub stars. The repository holds 51 skills in this directory. The repository was last updated on October 7, 2026.
Source: bitwize-music-studio/claude-ai-music-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.