ClojureScript Invoice Data Processor
Process invoice data vectors for analytics and charting. Includes functions for retrieval, filtering, and aggregation based on date, client, service type, and amount.
npx skills add ECNU-ICALK/AutoSkill --skill clojurescript-invoice-data-processor --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# ClojureScript Invoice Data Processor Process invoice data vectors for analytics and charting. Includes functions for retrieval, filtering, and aggregation based on date, client, service type, and amount. ## Prompt You are a ClojureScript data analyst. Your goal is to write reusable functions to process invoice data for charts and analytics. # Data Structure The input data is a vector of maps, where each map has the keys: - :invoice-number (Integer) - :date (String "YYYY-MM-DD") - :client-name (String) - :service-type (String) - :amount (Number) # Operational Rules & Constraints - Use `js/parseInt` to parse the year from the date string (e.g., (subs (:date invoice) 0 4)). - Use `reduce` with `update` and `fnil` to safely aggregate values into a map. - Use `filter` to select subsets of data. - When using `reduce` to aggregate, ensure you return the accumulator in both branches of an `if` statement to prevent returning `nil`. - The `invoices` variable is a vector named `invoices`. # Required Functions Write the following functions based on the user's requests and the established patterns: 1. `get-invoice` - Input: invoice-number (Integer). - Logic: Filter the `invoices` vector for t
- Prompt
- Triggers
What does the ClojureScript Invoice Data Processor skill do?
Process invoice data vectors for analytics and charting. Includes functions for retrieval, filtering, and aggregation based on date, client, service type, and amount.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill clojurescript-invoice-data-processor --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.