Agent skill
ksrc
Search/read 3rd-party Gradle dependency sources. Avoid directly accessing `.gradle`; instead, proactively use this skill to inspect source code of dependencies to learn API shapes or implementations.
Install this agent skill to your Project
npx add-skill https://github.com/respawn-app/ksrc/tree/main/skills/ksrc
SKILL.md
- Search dependencies to retrieve coordinates and matches using rg-style globs:
ksrc search "class LocalDate\("
If you want faster execution & less noise, consider adding:
--artifactto limit search to one artifact, (or--moduleto also limit by version)--subprojectto help discovery for monorepos/large modular apps--targetsto limit to specific KMP targets.
- Read a file by returned id:
ksrc cat org.jetbrains.kotlinx:kotlinx-datetime:0.7.1!/kotlinx/datetime/LocalDate.kt --lines 1,200
File-id format: group:artifact:version!/path/inside/jar.ext — works for any language in the source JAR (e.g. .kt, .java, .groovy)
Give this tool generous timeouts. It can take a few minutes to download sources and set up gradle.
Common issues
- If, unexpectedly, no matches are found, try
--projectwith app project (not monorepo root), specifying--scope(esp. for build-time deps), orksrc doctor. E_NO_SOURCES: dependency sources not available; tryksrc deps,ksrc fetch <coord>, specify a project and scope.- Gradle not found: a) run in a Gradle project dir, b) set
--projectpath explicitly, c) install gradle on machine. - Gradle build script is failing in the repo:
ksrcfalls back to cache-only resolution and warns; re-run with-vto see Gradle output for debugging. - Gradle fails with unresolved class version: User's Local java in env is resolved to something unsupported by gradle. Help them fix Gradle<>JDK incompatibility.
- Ambiguous modules: use
--module,--group, or--artifactto narrow scope.
Commands
ksrc search <pattern> [-- <rg-args>]
Search dependency sources.
Output format: <file-id> <line>:<col>:<match>
Common flags:
--allsearch across all resolved deps (default, slow)--project <path>project root (default.)--subproject <name>limit to a subproject (repeatable)--targets <list>limit KMP targets (comma‑separated:jvm,android,iosX64)--config <name>resolve specific configuration(s) (comma‑separated)--scope <compile|runtime|test|all>--module <glob>module filter (group:artifact[:version])--group <glob>/--artifact <glob>/--version <glob>--offlineonly use cached sources--refreshforce dependency refresh--context <n>shortcut forrg -C <n>(context lines emit column0)--rg-args <args>extra rg args (comma‑separated)-- <rg-args>pass through raw rg args--show-extracted-pathinclude temp extracted paths in output (off by default)
ksrc cat <file-id|path>
Print file contents.
Common flags:
--lines <start,end>1‑based inclusive range--module <glob>/--group/--artifact/--versionto disambiguate when using a path
ksrc open <file-id|path>
Open in $PAGER (defaults to less -R). Same flags as cat.
ksrc deps
List resolved dependencies and source availability.
ksrc resolve
Resolve and print source JARs: group:artifact:version|/path/to/sources.jar.
ksrc fetch <coord>
Ensure sources for a coordinate exist: group:artifact:version. Usually only needed with offline mode.
ksrc where <path|coord>
Locate cached source JAR or file.
ksrc doctor
Basic diagnostics for environment issues.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
ubiquitous-language
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
every-style-editor
This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for grammar, punctuation, mechanics, and style guide compliance.
manage-codex
Autonomous Codex batch orchestrator. Use for "/manage-codex", "manage codex", "use codex", "dispatch to codex", or long-running Codex work.
seo-audit
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.
capture-learning
Analyze recent conversation context and capture learnings to project knowledge files (for project-specific insights) or skills/commands/subagents (for cross-project patterns). Use when the user asks to "capture this learning", "update the docs with this", "remember this for next time", "document this issue", "add this to CLAUDE.md", "save this knowledge", or "update project knowledge". Also triggers after resolving build/setup issues, discovering non-obvious patterns, or completing debugging sessions with valuable insights.
agent-changelog
Compile an agent-optimized changelog by cross-referencing git history with plans and documentation. Use when asked to "update changelog", "compile history", "document project evolution", or proactively after major milestones, architectural changes, or when stale/deprecated information is detected that could confuse coding agents.
Didn't find tool you were looking for?