expense-tracker

Key things to consider before installing or running this skill: - Metadata mismatch: The registry metadata does not declare required environment variables, but both SKILL.md and the code require NOTION_API_KEY and EXPENSE_DATABASE_ID. Expect the skill to fail or prompt for those values unless fixed. Ask the publisher to update the metadata to list the Notion token as the primary credential. - Feature mismatch: SKILL.md lists interactive commands and summary/budget features that are not implemented in expense_tracker.py. If you need those features, request an updated implementation or avoid relying on the claimed functionality. - Credentials handling: The skill needs your Notion integration token and database ID. Only provide tokens scoped to a dedicated Notion integration (least privilege) and avoid sharing tokens that grant access to other unrelated workspaces or data. Consider creating a separate integration with limited permissions and sharing only the specific database. - Run safely: Because this is an included Python script that will make network requests, run it in a sandboxed environment (or review and run the code locally) rather than granting it broad system or credential access in production. Inspect or run the script locally to confirm behavior before allowing an agent to invoke it autonomously. - Ask for fixes: Request that the skill author (1) update registry metadata to declare required env vars and primary credential, (2) either implement the documented commands or remove them from SKILL.md, and (3) document expected HTTP response codes/behavior for Notion API errors. After those fixes, re-evaluate. If you want, I can produce a short checklist or a suggested metadata patch to send to the skill author to address these issues.