More screenshots
Works with the AI Agents you already use
Enterprise RAG and Governance
Connect sources, control access, keep indexes fresh and cite sources. 10 ordered skills, starting with Enterprise Semantic Search, Internal Knowledge Assistants, RAG Access Control.
Free
Enterprise RAG and Governance
Example session with this skill installed
Design an access control schema for a vector index that aggregates data from SharePoint and Jira, ensuring users only see documents they have permission to access.
- Read your context and instructions
- Compiled the enterprise rag
I have designed a RAG access control schema that synchronizes source permissions into your vector database to enable query-time filtering.
Enterprise RAG Access Control Schema
| Field Name | Type | Description | Purpose |
|---|---|---|---|
doc_id | String | Immutable source ID (e.g., SharePoint GUID) | Stable reference for updates |
acl_metadata | Array | List of User IDs, Group IDs, or Roles | Filter target for query-time enforcement |
visibility_level | Enum | public, internal, restricted, confidential | Secondary filter for safety overrides |
tenant_id | String | Unique ID for the organization or department | Hard partitioning in multi-tenant setups |
last_synced_at | Timestamp | ISO 8601 date of last permission sync | Audit for permission-sync lag |
source_system | String | sharepoint, jira, confluence | Namespace to prevent ID collisions |
Query-Time Enforcement Logic
To prevent leakage, every retrieval request must include a filter block. For a user with ID u_123 and groups g_456, g_789:
{
"vector": [0.12, 0.45, ...],
"filter": {
"and": [
{ "tenant_id": "org_alpha" },
{
"or": [
{ "acl_metadata": { "contains": "u_123" } },
{ "acl_metadata": { "contains_any": ["g_456", "g_789"] } }
]
}
]
},
"top_k": 5
}
Next steps
- Map your Identity Provider (Okta/AD) group IDs to the corresponding IDs in your SharePoint and Jira metadata.
- Implement a "deny-by-default" middleware in your retrieval service that injects these filters before hitting the vector store.
- Run an adversarial test by querying with a user ID known to lack access to a specific restricted document.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Companies deploying internal knowledge assistants often need a repeatable process, not a one-off prompt. This pack targets: Connect sources, control access, keep indexes fresh and cite sources.
What's inside (10 skills, suggested learning order)
- Enterprise Semantic Search — Deploy meaning-based search on intranets.
- Internal Knowledge Assistants — Chatbots over company documentation and wikis.
- RAG Access Control — Apply per-user permissions to retrieval.
- Incremental Index Updates — Keep vector stores in sync.
- Citations and Source Traceability — Attribute answers to verifiable passages.
- Enterprise Data Connectors — Integrate SharePoint, Drive, Slack and CRMs with LLMs.
- Knowledge Base Curation — Structure and maintain source content for AI.
- Technical Documentation for AI — Write documentation optimized for LLM consumption.
- Email, Chat and Ticket Indexing for Search — Make internal conversations searchable by meaning.
- Conversation Memory with Retrieval — Combine chat history and RAG.
Why a skill pack instead of a one-off prompt
Each skill gives the agent a defined trigger, step-by-step procedure and output format, so results are consistent across sessions and easier to review.
How to use
- Install the pack in your SKILL.md-compatible agent.
- Ask for the task in plain language.
- Review the output against the skill's quality checks before using it.
Known limitations
- Outputs are drafts that need human review; they are not professional, legal or financial advice.
- Tools, APIs and prices change; check current vendor documentation before relying on version-specific details.
- Quality depends on the context you give the agent (data, requirements, constraints).
- Tested only where stated in the Compatibility note.
Also by Rodrigo Santos
Specialized Agents and Distribution; AI Agents: Fundamentals and Protocols; Model Fine-Tuning and Alignment
Focuses on design and logic. Infrastructure, embedding models, and legal/HR approvals for data access must be provided by the user.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 3 days ago
- Free with an Agensi account
Requires