Rag based on Google drive

Use the Google Drive RAG CLI to search your synced personal documents, add tracking folders, or check the service account status.

Security Scan

The skill's stated purpose (a Google Drive RAG CLI) matches the included CLI code, but the runtime instructions require and store sensitive environment values (API_URL and JWT_TOKEN) that are not declared in the skill metadata and include ambiguous instructions to auto-renew/update tokens — this mismatch and the storage/handling of credentials are concerning.

Purpose & Capability

The name/description (RAG for Google Drive) align with the included cli.py which talks to a RAG service. However, the skill metadata declares no required environment variables or primary credential while the SKILL.md and cli.py clearly require API_URL and JWT_TOKEN at runtime. That metadata omission is an incoherence.

Instruction Scope

SKILL.md instructs the agent to create and use a ~/.agents/skills/driverag/.env file containing API_URL and JWT_TOKEN and to run the CLI from the skill directory and venv. It also tells the agent to automatically run renew-token on 401s and to update the .env file — giving the agent discretion to write credentials to disk. The CLI contacts an arbitrary API_URL provided by the user; if that URL is untrusted it will receive the JWT_TOKEN. These file- and credential-writing instructions broaden scope beyond a simple search helper and could enable inadvertent credential storage or exfiltration.

Install Mechanism

No install spec in registry (instruction-only), but SKILL.md asks to create a Python venv and pip install requirements.txt. requirements.txt is minimal (requests, python-dotenv). This is moderate/expected for a bundled Python CLI and does not itself look suspicious.

Credentials

The skill requires two sensitive environment values at runtime (API_URL and JWT_TOKEN) but the registry metadata lists none and no primary credential. Requiring a JWT and service endpoint is reasonable for a RAG service, but failing to declare them in metadata is a mismatch that reduces transparency. Additionally, SKILL.md directs storing JWT_TOKEN in a skill-local .env file and suggests automatically renewing/updating tokens — this increases the chance tokens are persisted and handled by the agent without clear user consent.

Persistence & Privilege

always:false (good). The skill instructs the agent to create files under ~/.agents/skills/driverag/ (venv and .env) and to run commands there; writing those files is normal for an instruction-only skill that includes a CLI, but it means the agent will hold persistent credentials in its skill directory if the user follows instructions. The ability to autonomously invoke renew-token combined with writing .env could let the agent update stored credentials — this is not blocked by skill metadata and should be considered by the user.

What to consider before installing

Key things to consider before installing: - Metadata mismatch: The skill actually requires API_URL and JWT_TOKEN (sensitive) but the registry metadata doesn’t declare them — ask the publisher why these were omitted. - Trust the endpoint: The API_URL is arbitrary. Only provide an API_URL you trust; if it points to a malicious server it will receive your JWT_TOKEN and any requests made by the CLI. - Minimize privileges: If you must supply a token, prefer a scoped service account or token with the minimum permissions, not a full Google account credential. - Be cautious storing secrets: The skill instructs you to store credentials in ~/.agents/skills/driverag/.env. Storing tokens in skill directories can lead to persistent exposure; consider using a secure secret manager instead and avoid leaving long-lived tokens there. - Renew-token behavior: SKILL.md suggests automatically running renew-token and updating .env. The CLI prints the new token but does not itself write .env — watch for whether the agent will write the file for you. Don’t let the agent silently persist new credentials without explicit consent. - Verify outputs and logs: The CLI prints tokens on renew; those could be captured in logs. If you proceed, rotate tokens afterward and audit logs. - Ask for clarifications: Request the publisher to (1) declare required env vars in metadata, (2) document what the remote API_URL represents (who runs it), and (3) avoid instructions that automatically persist credentials. Given these mismatches and the sensitive handling of credentials, treat the skill as suspicious until the above issues are resolved or you can supply minimal, revocable credentials and a trusted API endpoint.

Google Drive RAG CLI Skill

When to use

Use this skill when the user asks you to search their personal documents via the Google Drive RAG API. This includes questions like "What is my Aetna ID?", "Search my drive for...", "Sync my drive", "What is the status of my sync?", "What is the service account email?", or "Renew my token".

Setup and Initialization

This skill includes a self-contained Python CLI tool in its directory.

Before running any commands, you MUST verify the environment is set up:

1. Check if ~/.agents/skills/driverag/.env exists.
   • If it DOES NOT exist, you MUST ask the user to provide their API_URL and JWT_TOKEN.
   • Once they provide them, create the .env file in the skill directory (~/.agents/skills/driverag/.env) with those values.
2. Check if the virtual environment exists (~/.agents/skills/driverag/venv).
   • If it DOES NOT exist, create it: cd ~/.agents/skills/driverag && python3 -m venv venv
   • Then install the requirements: source venv/bin/activate && pip install -r requirements.txt

Instructions

Once the environment is validated and the .env file is created, you can interact with the RAG system using the CLI tool.

ALWAYS run the CLI from the skill directory (~/.agents/skills/driverag/) and ALWAYS activate its virtual environment first.

Here are the commands you can run:

1. Search documents:

   cd ~/.agents/skills/driverag && source venv/bin/activate && python3 cli.py search "$ARGUMENTS"
   

   If the user passes specific folders, append them: python3 cli.py search "$ARGUMENTS" -f "Folder Name"

2. List all Indexed Files in the RAG Database:

   cd ~/.agents/skills/driverag && source venv/bin/activate && python3 cli.py list-files
   

3. Check Sync Status:

   cd ~/.agents/skills/driverag && source venv/bin/activate && python3 cli.py status
   

4. Sync documents:

   cd ~/.agents/skills/driverag && source venv/bin/activate && python3 cli.py sync
   

   To force a complete re-download and re-indexing of all files: python3 cli.py sync --force

5. Get Service Account Email:

   cd ~/.agents/skills/driverag && source venv/bin/activate && python3 cli.py service-account
   

6. Renew Token:

   cd ~/.agents/skills/driverag && source venv/bin/activate && python3 cli.py renew-token
   

7. Add a folder manually:

   cd ~/.agents/skills/driverag && source venv/bin/activate && python3 cli.py add-folder "$ARGUMENTS"
   

Important notes

• Do NOT hallucinate answers. ALWAYS run the cli.py search command to get the exact answer from the RAG system and output the exact response it gives you.
• CRITICAL: If the user asks "What files do you have", "List my files", or "What documents are in the database", DO NOT use the search command! You MUST use the list-files command instead, because RAG semantic search cannot generate file lists.
• If the CLI returns a 401 Unauthorized or warns that the token is about to expire, inform the user and automatically run the renew-token command to update their .env file.
• When outputting the RAG search results to the user, ensure you include the citations/source documents exactly as the CLI returns them so the user knows where the information came from.

Examples

• "Search my drive for my Aetna ID" -> Run the search command with "What is my Aetna ID?"
• "What files do you have in the database?" -> Run the list-files command.
• "What is the status of my sync?" -> Run the status command.
• "What email should I share my folders with?" -> Run the service-account command.
• "Renew my token" -> Run the renew-token command.