# Manage Nonprofit Receipt Scanning

Receipt workflows often require manual entry, OCR setup, and database checks across several scripts. This skill gives operators project-specific commands, schemas, and troubleshooting steps for receipt tools.

## Install

```bash
npx skillstore add egadams/receipt-scanning-tools
```

## Metadata

- Status: approved
- Slug: egadams-receipt-scanning-tools
- Skillstore revision: r1
- Version status: missing
- Tree hash: 59362dedb2abca1c31bc258c556c29380e8e1d96cdb479b14d18c75ec7a7243e
- Author: EGAdams
- GitHub username: EGAdams
- License: MIT
- Repository: https://github.com/EGAdams/planner/tree/main/nonprofit\_finance\_db/.claude/skills/receipt-scanning-tools
- Ref: 30c73eac2afe762f6aa9c4553158769369d47351
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem, env\_access
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/egadams-receipt-scanning-tools
- Manifest: https://skillstore.pages.dev/api/skills/egadams-receipt-scanning-tools/manifest

## Capabilities

- Identifies project paths, virtual environment setup, and receipt tool entry points.
- Documents database schemas for categories, merchants, expenses, and receipt metadata.
- Provides commands for manual receipt entry, deletion workflows, API service startup, and database checks.
- Shows Python patterns for merchant lookup, category hierarchy queries, and expense saving.
- Describes troubleshooting steps for missing modules, schema errors, and database connectivity.
- Lists planned enhancements for receipt upload, OCR integration, bulk import, and search.

## Use Cases

- Record Nonprofit Receipts: Use the manual entry workflow to select merchants, dates, amounts, categories, and save confirmed expenses.
- Maintain Receipt Tooling: Use the schema notes and code patterns to fix queries or add a new receipt command-line tool.
- Review Expense Data: Use the database check commands to inspect recent expenses, category counts, and connection status before changes.

## Prompt Templates

### Open the Receipt Menu

```
Use this skill to show me how to activate the project environment and open the receipt tools menu. Ask before running each command.
```

### Enter a Manual Receipt

```
Guide me through manual receipt entry for a nonprofit expense. Ask for merchant, amount, date, category, and confirmation before saving.
```

### Fix a Category Query

```
A query failed with an unknown category_path column. Use the documented schema to explain the issue and propose a safer category path query.
```

### Plan a New Receipt Tool

```
Create a plan for a new receipt validation command-line tool that follows the existing project patterns. Include database safety checks and test steps before any write operation.
```

## Limitations

- It depends on local project paths and database schemas that may not exist in another environment.
- It provides operational guidance, not the executable source files for the referenced tools.
- It requires database credentials and a Gemini API key to be configured outside the skill.
- Receipt upload, bulk import, and search are listed as future tasks, not current capabilities.

## Best Practices

- Confirm before running any command that writes, deletes, or initializes database records.
- Replace local absolute paths and sample names with values from the active project.
- Keep credentials in local secret storage and avoid sharing environment file contents.

## Anti Patterns

- Do not run database deletion or initialization commands without a backup and explicit approval.
- Do not paste API keys, database passwords, or environment file contents into chat.
- Do not treat schema examples as proof that production columns exist.

## Security Audit

- Audited at: 2026-07-05T15:04:43.118\+00:00
- Summary: Most external command and system reconnaissance alerts are false positives caused by Markdown code fences, inline paths, and SQL examples. Confirmed risks remain for machine-specific hidden filesystem paths, .env credential guidance, and direct access to nonprofit finance database records. No prompt injection attempt was found, but the skill exposes personal finance context and includes destructive database workflows.

## Stats

- Views: 282
- Downloads: 9
- Favorites: 0
- Popularity score: 0