agentleFS
Sign inStart free
SC32brSC32br/hermes-skill-veo-vertex/llms.txt

hermes-skill-veo-vertex

llms.txt2 starsChanged 6 months agoMITView on GitHub

System Prompt Constraints: Read this before modifying the codebase. This repository provides Video Generation capabilities for Hermes Agent via Google Cloud Vertex AI (Veo).

  • In this repositoryOne other file it gives its agents.

The file

We split this llms.txt into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Does not use keyless/ADC authentication.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 3,592 llms.txt files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
llms.txt
# Hermes Skill: Vertex AI Veo Video Generator

> **System Prompt Constraints:**
> Read this before modifying the codebase. This repository provides Video Generation capabilities for Hermes Agent via Google Cloud Vertex AI (Veo).

## Core Entities
- **Framework**: Hermes Agent
- **Target API**: Google Cloud Vertex AI
- **Models**: Veo 3.1
- **Cloud Infrastructure**: Vertex AI API + Google Cloud Storage (GCS)

## Architecture Overview
1. **Agent Workflow**: User prompt -> `SKILL.md` parser -> `scripts/generate.py` -> Vertex AI.
2. **Storage Dependency**: Unlike image generation, Veo requires a GCS bucket (`VEO_GCS_BUCKET`) to store the rendered `.mp4` video files.
3. **Authentication**: Strictly relies on Service Account JSON provided via `GOOGLE_APPLICATION_CREDENTIALS` and `GOOGLE_CLOUD_PROJECT`.

## Known Caveats
- Requires `google-cloud-aiplatform` and `google-cloud-storage` libraries in the Hermes virtual environment.
- Does not use keyless/ADC authentication. JSON service accounts are mandatory.
- Long-running operations (LRO): Video generation is asynchronous. The script must handle polling/waiting for the GCS payload to finalize before returning the absolute media path to the Orchestrator.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free