people-property
Search for people and properties using Whitepages APIs via x402. USE FOR: - Finding people by name and location - Address lookups and verification - Property owner information - Background research (with legitimate purpose) TRIGGERS: - "find person", "lookup person", "who lives at" - "property owner", "property search", "address lookup" - "person at address", "contact info for" IMPORTANT: These endpoints contain personal information. Use responsibly and only for legitimate purposes. See rules/privacy.md for guidance. Use `npx agentcash fetch` for Whitepages endpoints. Both endpoints are $0.44 per call.
Install with Tessl CLI
npx tessl i github:Merit-Systems/agentcash-skills --skill people-property89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities, natural trigger terms users would actually say, explicit guidance on when to use it, and a distinctive niche that won't conflict with other skills. The structured format with USE FOR and TRIGGERS sections makes it highly scannable and actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Finding people by name and location', 'Address lookups and verification', 'Property owner information', 'Background research'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (search for people and properties via Whitepages APIs) and when (explicit TRIGGERS section with 'find person', 'property owner', etc.). The USE FOR and TRIGGERS sections provide explicit guidance on when to select this skill. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural user phrases: 'find person', 'lookup person', 'who lives at', 'property owner', 'address lookup', 'contact info for'. These are terms users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific niche: Whitepages APIs, people/property lookups, x402 payment system. The combination of personal information lookup via specific API provider creates a clear, non-conflicting identity. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable API documentation with executable examples and good organization. The main weaknesses are some redundancy in examples and workflows that lack concrete validation steps for verifying results or handling errors. Cost considerations and limitations sections add practical value.
Suggestions
Add concrete validation guidance in workflows - specify what fields to check to confirm a match (e.g., 'verify age range and address history align with known information')
Consolidate the two person search examples into one with a comment showing optional fields, reducing redundancy
Add error handling guidance - what does a failed search return and how should Claude respond to no results or multiple ambiguous matches
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some redundancy - the 'More Specific Search' example largely duplicates the first example with minor additions, and the response field documentation could be more compact. The limitations section and some workflow descriptions add modest padding. | 2 / 3 |
Actionability | Provides fully executable bash commands with complete JSON payloads that are copy-paste ready. Parameters are clearly documented with required/optional status, and return values are explicitly listed. | 3 / 3 |
Workflow Clarity | Workflows include checklists but lack validation/verification steps for confirming results are correct or handling errors. The 'Verify results match expected person' step is vague - no concrete guidance on what to check or how to handle mismatches. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections, appropriate references to external files (rules/getting-started.md, rules/privacy.md), and a logical flow from quick reference to detailed usage to workflows. Navigation is straightforward. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.