Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
pii-detect - Skill - OpenSmartRoute
Skillv1.0.0
pii-detect
Detect and flag personally identifiable information (PII) in text, code, and configurations. Use before committing code, writing logs, storing data, or sending model responses that might contain…
Imported from ruvnet/ruflo (plugins/ruflo-aidefence/skills/pii-detect/SKILL.md) via skills.sh. Install upstream with npx skills add ruvnet/ruflo --skill pii-detect. Copyright stays with the author.
PII Detection
Detect personally identifiable information before it enters logs, commits, or responses.
When to use
Before committing code, storing data, or sending responses that might contain PII (emails, phone numbers, SSNs, API keys, passwords).
Steps
Quick PII check — call mcp__plugin_ruflo-core_ruflo__aidefence_has_pii with the text for a boolean result
Detailed scan — call mcp__plugin_ruflo-core_ruflo__transfer_detect-pii for categorized PII findings
Full analysis — call mcp__plugin_ruflo-core_ruflo__aidefence_analyze for context-aware PII detection
If PII found, flag the specific locations and suggest redaction
PII categories detected
Email addresses, phone numbers
Social security numbers, tax IDs
Credit card numbers
API keys, tokens, passwords
Physical addresses
Names linked to sensitive data
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-s-X POST https://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install pii-detect and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
