Set up GBrain with auto-provision Supabase or PGLite, AGENTS.md injection, first import
59
70%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Fix and improve this skill with Tessl
tessl review fix ./skills/setup/SKILL.mdSecurity
1 high severity finding. You should review these findings carefully before considering using this skill.
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
The skill asks the user for database connection strings, OAuth client secrets, access tokens, and service-role keys and shows them being embedded verbatim into CLI commands and config files (e.g., --url "<connection_string>", --oauth-client-secret <secret>, SUPABASE_ACCESS_TOKEN, serviceRoleKey), which requires the LLM to handle/output secrets directly and creates exfiltration risk.
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
The skill's install step runs "bun install -g github:garrytan/gbrain#latest-stable", which fetches and installs remote code from the GitHub repo at runtime (github:garrytan/gbrain#latest-stable), satisfying the criteria for executing external code during setup.
055ac6c
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.