📦

vectoree

Name: vectoree
Author: vectoreeai

v0.9.0 Inhaltsrevision r1 Mittleres Risiko 🌐 Netzwerkzugriff🔑 Umgebungsvariablen⚙️ Externe Befehle📁 Dateisystemzugriff

Connect Apps and Agents to Vectoree Cloud

Connecting models, authentication, data, and agent tools can require separate integration workflows. This skill provides Vectoree CLI playbooks and server-side integration guidance.

Unterstützt: Claude Codex Code(CC)

⚠️ 50 Schlecht

Maintain this Skill? Claim it ⚠️ 50 Schlecht

Mit meinem Agent installieren

Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.

Agent-Anfrage

Review the Skillstore skill "vectoree" from https://skillstore.io/skills/vectoreeai-vectoree.md and its manifest at https://skillstore.io/api/skills/vectoreeai-vectoree/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.

Agent-lesbare Ressourcen

Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.

Markdown-Detailseite GET /skills/vectoreeai-vectoree.md Signiertes manifest GET /api/skills/vectoreeai-vectoree/manifest Signiertes lockfile GET /api/skills/vectoreeai-vectoree/lockfile

Testen

„vectoree“ wird verwendet. Check an already linked project's Vectoree connection without changing settings.

Erwartetes Ergebnis:

Example result: the current directory is linked to a Vectoree project.
Existing login and project settings remain unchanged.
Credentials are omitted from the report.

„vectoree“ wird verwendet. Plan app-user login with email verification.

Erwartetes Ergebnis:

Integration plan: the browser submits to the application's backend-for-frontend.
The backend uses a scoped project key to call Vectoree App Auth.
Registration and verification use an eight-digit email code.
OAuth setup remains with the project owner when provider credentials are missing.

„vectoree“ wird verwendet. Review the proposed Codex provider setup.

Erwartetes Ergebnis:

Review result: back up existing configuration and preserve unrelated MCP entries.
Configure the requested Vectoree provider with a project or employee key.
Do not run the remote installer until its contents and integrity have been verified.

Sicherheitsaudit

Mittleres Risiko

v1 • 21.10.2026 Versionsbericht öffnen

Most static matches are Markdown delimiters, placeholders, or documented server-side authentication and configuration. Four URL findings recommend executing mutable remote installers without integrity verification. Additional workflow risks include unsolicited search-server replacement and persistent installation of mutable remote instructions; no evidence found of deliberate credential exfiltration.

Gescannte Dateien

1,006

Analysierte Zeilen

Prüfelemente

Falschmeldungen ignoriert

Bestätigte Sicherheitsbedenken (2)

Mittel

SKILL.md:174-179 scenarios/tool-hub.md:15-32

Search setup examples can remove existing providers without a switch request

The add-search example uses --replace-search, although the playbook reserves removal for an explicit switch request. Following it can delete working search integrations without authorization.

The intent table distinguishes adding from switching, but the shared commands always include the removal flag. This directly contradicts the stated preservation rule.

Mittel

SKILL.md:59-65 SKILL.md:320-331

Mutable remote instructions become persistent agent guidance

Setup says, "Also save the latest copy of this file into the agent skill directory and enable it." Missing playbooks load from mutable main-branch URLs without review or integrity checks, allowing later upstream changes to become trusted agent instructions.

The text explicitly enables the latest remote copy and offers mutable playbook fallbacks. No version pin or content-integrity gate is specified for these instructions.

Elemente der Fähigkeitsprüfung (4)

Dies sind echte lokale Fähigkeiten, die für diese Fähigkeit erwartet werden können; daher müssen sie überprüft werden, werden jedoch nicht als bestätigtes bösartiges Verhalten gezählt.

Hoch

scenarios/model-gateway.md:155

Hardcoded URL

bash <(curl -fsSL https://vectoree.ai/scripts/codex-vectoree-setup.sh)

The command executes a freshly downloaded shell script without integrity verification or prior inspection. A compromised response would run with the user's shell privileges.

Hoch

scenarios/model-gateway.md:160

Hardcoded URL

irm https://vectoree.ai/scripts/codex-vectoree-setup.ps1 | iex

The command pipes a freshly downloaded PowerShell script directly to Invoke-Expression. No pinned artifact, signature check, or prior inspection protects the user's environment.

Hoch

SKILL.md:291

Hardcoded URL

bash <(curl -fsSL https://vectoree.ai/scripts/codex-vectoree-setup.sh)

The example prompt tells the agent to run a downloaded shell script immediately. No integrity verification or inspection protects local credentials and configuration.

Hoch

SKILL.md:293

Hardcoded URL

irm https://vectoree.ai/scripts/codex-vectoree-setup.ps1 | iex

The example prompt pipes remote PowerShell content directly into execution. The mutable script is not pinned or verified before obtaining local execution privileges.

Risikofaktoren

🌐 Netzwerkzugriff (31)

🔑 Umgebungsvariablen (23)

⚙️ Externe Befehle (50)

📁 Dateisystemzugriff (8)

scenarios/model-gateway.md:147 scenarios/model-gateway.md:171 scenarios/model-gateway.md:187 scenarios/model-gateway.md:147 scenarios/model-gateway.md:171 scenarios/model-gateway.md:187 scenarios/tool-hub.md:81 scenarios/tool-hub.md:81

Geprüft von: codex

Diesen Bericht teilen & zitieren

Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.

Versionsbericht öffnen

Berichtslink kopieren

https://skillstore.io/skills/vectoreeai-vectoree/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown-Badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/vectoreeai-vectoree/security.svg)](https://skillstore.io/skills/vectoreeai-vectoree?utm_source=security_passport_badge)

HTML-Badge

<a href="https://skillstore.io/skills/vectoreeai-vectoree?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/vectoreeai-vectoree/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Einbettungskarte

<iframe src="https://skillstore.io/embed/skills/vectoreeai-vectoree.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Wissenschaftliche Zitate (APA · BibTeX · CFF)

APA-Zitat

vectoreeai. (2026). vectoree security audit report (audit version 1) [Author version 0.9.0]. Skillstore. https://skillstore.io/skills/vectoreeai-vectoree/audits/1

BibTeX-Zitat

@techreport{vectoreeai-vectoreeai-vectoree-2026,
  author = {vectoreeai},
  title = {vectoree security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/vectoreeai-vectoree/audits/1},
  note = {Author version 0.9.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "vectoree security audit report (audit version 1)"
version: "0.9.0"
type: report
authors:
  - name: "vectoreeai"
date-released: "2026-10-21"
url: "https://skillstore.io/skills/vectoreeai-vectoree/audits/1"
identifiers:
  - type: other
    value: "skillstore:vectoreeai-vectoree:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore-Score

Warum dieser Score Evidenzvertrauen: Mittel

Architektur

100

Wartbarkeit

Inhalt

Gemeinschaft

Spezifikationskonformität

Was Sie erstellen können

Build an application backend

Connect a project and add app-user login, persistent records, and image uploads through documented server-side integration paths.

Integrate model capabilities

Discover available models, test the requested modality, and adapt existing SDK calls to the Vectoree gateway.

Configure coding-agent services

Add hosted MCP tools or configure a requested Codex provider change while preserving unrelated settings.

Diese Prompts ausprobieren

Check project connection

Check this project's Vectoree connection. Report the linked project without printing credentials or changing configuration. Ask before making any billable validation call.

Add server-side chat

Add a Vectoree chat route to this application. Discover a suitable model, keep the project key server-side, and request approval before a billable test.

Add app-user authentication

Add Vectoree app-user login with email verification. Use a server-side BFF and scoped auth key. Keep developer Cloud login separate.

Plan a Codex provider change

Prepare a Vectoree provider configuration for Codex. Show a minimal configuration diff and backup plan. Do not execute remote installers or modify settings without approval.

Bewährte Praktiken

Keep scoped project credentials server-side and exclude credential-bearing environment and MCP files from version control.
Review and verify downloaded installers and skill updates before executing or enabling them.
Confirm provider changes, search replacement, destructive SQL, and billable validation calls before proceeding.

Vermeiden

Expose project secrets in browser bundles, public environment variables, logs, or committed configuration.
Replace existing search providers or change Codex configuration without an explicit request.
Treat authentication, model, or storage commands as interchangeable, or invent unsupported platform APIs.

Häufig gestellte Fragen

Does this skill include the Vectoree CLI?

No. It provides instructions that call the external Vectoree CLI and documented service endpoints.

Can this skill work without a Vectoree account?

Cloud operations need project access and appropriate credentials. Reviewing the playbooks does not require an account.

Where should project API keys be stored?

Use server-side configuration and exclude credential-bearing files from git. Never expose project keys in browser bundles or printed results.

Are model and tool tests free?

Do not assume they are free. Model calls, Tool Hub requests, and app authentication email can consume the organization wallet.

Can it configure Codex to use Vectoree?

Yes, the playbook documents provider configuration and backup guidance. Its remote installer examples require independent inspection and integrity verification.

Does it deploy applications or provide signed storage URLs?

No. Self-service deployment and CLI signed-URL commands are outside the documented launch scope.