db-search
Skill0 starsChanged 3 months agoMITView on GitHub
Search for database objects (tables, stored procedures, views, functions) in the scripted-out DB sources. Use when looking for table schemas, SP definitions, or exploring database structure.
In this repository27 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- buildSkill
- cleanup-worktreeSkill
- db-querySkill
- dd-errorsSkill
- devops-wiki-updateSkill
- devops-workitem-createSkill
- devops-workitem-readSkill
- devops-workitem-updateSkill
- finalize-taskSkill
- find-codeSkill
- merge-mainSkill
- panel-review-fixSkill
- panel-reviewSkill
- prSkill
- rebase-mainSkill
- starttaskSkill
- testSkill
- ask-codexSkill
- ask-geminiSkill
- councilSkill
- dailySkill
- find-sessionSkill
- merged-prsSkill
- mm-notifySkill
- optimize-promptSkill
- qSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 43
If searching content: which objects reference the term
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Database Object Search
Search term: $ARGUMENTS
Your task
Parse the arguments to determine:
- search-term: The pattern to search for (required)
- object-type:
table,sp(stored procedure),view, orfunction(optional, defaults to all) - database:
MainDborAccountsDb(optional, defaults to both)
Search locations
Database sources are scripted out nightly (one file per object) into /c/work/DbScripts/sources/:
| Database | Tables | Stored Procedures | Views | Functions |
| MainDb | /c/work/DbScripts/sources/MainDb/tables/ | /c/work/DbScripts/sources/MainDb/storedprocedures/ | /c/work/DbScripts/sources/MainDb/views/ | /c/work/DbScripts/sources/MainDb/functions/ |
| AccountsDb | /c/work/DbScripts/sources/AccountsDb/tables/ | /c/work/DbScripts/sources/AccountsDb/storedprocedures/ | /c/work/DbScripts/sources/AccountsDb/views/ | /c/work/DbScripts/sources/AccountsDb/functions/ |
Search strategy
- Find by filename (object name contains search term):
ls /c/work/DbScripts/sources/{db}/{type}/ | grep -i "search-term" - Find by content (object references search term):
rg -l -i "search-term" /c/work/DbScripts/sources/{db}/{type}/
Output
Report:
- Matching object names (files)
- If searching content: which objects reference the term
- Offer to read specific files if the user wants to see definitions
Note
The scripted files can drift behind the live database (hotfixes applied directly by DBAs). For the authoritative definition of a stored procedure, query sys.sql_modules on staging (see CLAUDE.md).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.