Data access restrictions for logged-in user in mobile
Free account. Installing gives you the manifest plus copy-paste snippets.
See reviewsInstruction file imported from AQUILA04/ELYKIA (
.cursor/rules/user-specific-data-access.mdc). Copyright stays with the author.
All data requests must be filtered by the logged-in user (e.g., 'commercialUsername'). The solution must be generic to handle different column names ('commercial', 'commercialId', 'commercialUsername') based on the entity. This ensures users only access their authorized data.
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 slot
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
{
"ocm": "1",
"id": "aquila04-elykia-user-specific-data-access-rule",
"kind": "skill",
"name": "user-specific-data-access",
"description": "Data access restrictions for logged-in user in mobile",
"publisher": "AQUILA04",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github-cursor-rules"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Data access restrictions for logged-in user in mobile"
],
"primary": false,
"metadata": {
"source": {
"provider": "github-cursor-rules",
"repository": "https://github.com/AQUILA04/ELYKIA",
"path": ".cursor/rules/user-specific-data-access.mdc",
"ref": "84312fa7c17aea36aa8575884e3b6b3a65ef376f",
"url": "https://github.com/AQUILA04/ELYKIA/blob/84312fa7c17aea36aa8575884e3b6b3a65ef376f/.cursor/rules/user-specific-data-access.mdc",
"key": "AQUILA04/ELYKIA/.cursor/rules/user-specific-data-access.mdc"
},
"applies_to": "mobile/**"
},
"instructions": "# User Specific Data Access\n\nAll data requests must be filtered by the logged-in user (e.g., 'commercialUsername'). The solution must be generic to handle different column names ('commercial', 'commercialId', 'commercialUsername') based on the entity. This ensures users only access their authorized data.",
"cost": {
"context_tokens": 76
}
}Fetch it by URL: GET /api/v1/registry/aquila04-elykia-user-specific-data-access-rule/manifest?version=1.0.0
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.