Api Filtering Sorting
CheckedProvides API guidance and assistance for agent workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add secondsky/claude-skills --skill api-filtering-sorting -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
secondsky
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned secondsky/claude-skills at 8837836131.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 8837836131
- Scanned
- 1 file, 83 lines
About this skill
What it does
This skill enables AI agents to build flexible filtering and sorting systems for API endpoints, allowing them to handle complex queries efficiently. It provides guidance on constructing query parameters and implementing backend logic (using Node.js as an example) to process these requests securely and effectively. The system supports a range of operators for filtering data based on various criteria.
When to use it
- When building APIs that require users to filter and sort data.
- To implement secure and efficient API endpoints that prevent injection vulnerabilities.
- For scenarios where complex queries need to be handled without impacting performance.
- When you want to provide a standardized way for agents to request specific subsets of data from an API.
Key capabilities
- Query Parameter Syntax: Supports GET requests with parameters like
/products?category=electronics&price[gte]=100&price[lte]=500&sort=-price,name. - Filter Parsing: Parses query parameters to extract filter criteria and operator types (eq, ne, gt/gte, lt/lte, in, like).
- Sort Parsing: Parses sort parameters, handling ascending and descending order.
- Whitelist Enforcement: Allows only pre-defined fields for filtering and sorting.
- Input Validation: Validates data types of filter values (e.g., converting strings to numbers or booleans).
Example prompts
- "Generate a Node.js API endpoint that filters products by category 'electronics' and price between 100 and 500, sorted by price descending then name."
- "Show me how to implement filtering for the 'status' field using the 'ne' (not equals) operator in my API."
- “What’s the recommended syntax for sorting products alphabetically?”
Tips & gotchas
- The skill provides a Node.js implementation example, but the concepts are applicable to other backend languages.
- Security is paramount: always whitelist allowed filter fields and validate input types to prevent vulnerabilities.
- Performance can be improved by indexing frequently filtered columns in your database.