# Add Gradle Dependencies with Approval

Adding libraries without review can create version drift and unnecessary maintenance. This skill guides approval, version discovery, catalog updates, and build verification.

## Install

```bash
npx skillstore add anysoftkeyboard/add-dependency
```

## Metadata

- Status: approved
- Slug: anysoftkeyboard-add-dependency
- Skillstore revision: r2
- Version status: missing
- Tree hash: a512e09b94cea66360f8615dba14e5a9c4af22df7ecc4088bcbcb711caac67df
- Author: AnySoftKeyboard
- GitHub username: AnySoftKeyboard
- License: MIT
- Repository: https://github.com/AnySoftKeyboard/janus/tree/main/.claude/skills/add-dependency
- Ref: 89edfdc710d0846129dcee6a929477b04f08052c
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/anysoftkeyboard-add-dependency
- Manifest: https://skillstore.pages.dev/api/skills/anysoftkeyboard-add-dependency/manifest

## Capabilities

- Evaluates whether a third-party dependency is necessary before modifying project files.
- Requires user approval and explains why alternatives were not selected.
- Directs a web search for the latest stable library version.
- Adds version and library entries to the Gradle version catalog.
- Runs a relevant Gradle build task to verify dependency resolution.

## Use Cases

- Add an Android Library: Introduce a stable Android library through the shared version catalog and verify the affected build.
- Review a Dependency Proposal: Compare a proposed library with existing solutions before approving repository changes.
- Standardize Automated Changes: Guide an AI coding tool through a consistent approval and verification process.

## Prompt Templates

### Add One Library

```
Add [library] to this Gradle project. Explain why it is needed and ask for approval before changing files.
```

### Compare Alternatives

```
Evaluate [library] against [alternative]. Recommend whether to add it, verify the latest stable version, then wait for approval.
```

### Update the Version Catalog

```
Add [group]:[artifact] through gradle/libs.versions.toml after approval. Use clear aliases, then run the relevant Gradle build task.
```

### Audit and Implement

```
Audit this dependency for necessity, maintenance, compatibility, and catalog consistency. Compare alternatives, obtain approval, implement it, and verify the affected build.
```

## Limitations

- Designed for Gradle projects that use a version catalog.
- Does not perform license, vulnerability, or supply-chain analysis.
- Requires web access to verify the current stable version.
- Cannot guarantee compatibility beyond results from the selected build task.

## Best Practices

- Confirm the dependency is necessary and discuss alternatives before requesting approval.
- Verify the stable version from authoritative sources because search results can be stale.
- Run the narrowest relevant Gradle task after updating the version catalog.

## Anti Patterns

- Do not edit project files before explicit approval unless autonomous changes were already approved.
- Do not hardcode dependency versions in Gradle build files.
- Do not select prerelease or dynamic versions when a stable release is required.

## Security Audit

- Audited at: 2026-07-23T04:59:07.007\+00:00
- Summary: All seven detections are false positives caused by Markdown formatting or benign prose. The executable example is a fixed Gradle build command without dynamic input. No prompt injection or malicious intent was found.

## Stats

- Views: 187
- Downloads: 8
- Favorites: 0
- Popularity score: 0