SQL Connector

Generic SQL Server connectivity for OpenClaw agents. Use when: (1) executing parameterized queries against SQL Server, (2) building repository layers that ne...

This skill appears to implement the SQL Server connector it advertises, but there are a few red flags you should consider before installing: - Required env vars are not declared in the registry metadata. The connector expects SQL_CLOUD_*/SQL_LOCAL_* (or SQL_{IDENT}_*) variables in an .env or the process environment. Confirm you are willing to provide database credentials to this skill. - The code calls load_dotenv(..., override=True) when it finds a .env. That will overwrite existing environment variables with values from the file, which can be surprising and could unintentionally change other services' behavior. Consider storing credentials in a secure secret store or verifying .env contents before installation. - Some config (SQL_DEFAULT_BACKEND) is read at import time before .env is loaded, so behavior can differ depending on how the module is imported. Test in your environment to ensure the connector picks up the intended backend. - The README suggests installing via pip; prefer to review the pip package source or pin an exact version, and run the bundled tests in an isolated environment (or read the code) to confirm no unwanted network or file operations occur. - If you plan to use this in production, prefer least-privilege DB credentials and network isolation (restrict DB user permissions and network access). If you need higher assurance, request the maintainer update the package metadata to declare required env vars and to stop overriding environment variables by default. If you want, I can list the exact lines in the code that implement the .env loading, the override behavior, and the import-time default reads so you can review or point them to the maintainer.

Type: OpenClaw Skill Name: sql-connector Version: 2.2.0 The sql-connector skill is a well-structured and legitimate SQL Server interface for OpenClaw agents. It demonstrates strong security practices, such as using a metaclass (_SealCoreMethods in sql_connector.py) to enforce parameterized queries and prevent SQL injection by sealing core execution methods. The code handles credentials safely via environment variables and includes comprehensive documentation and unit tests that align with its stated purpose.