test-model
Skill524 starsChanged 3 days agoApache-2.0View on GitHub
Test a model end-to-end using the xybrid execution system.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- guoqingbao/vllm.rstheir own version, first seen Oct 8, 2026
- Pipelex/pipelextheir own version, first seen Feb 25, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Pipelex/pipelex★ 951same name
- guoqingbao/vllm.rs★ 345same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- xybrid-connectSkill
- xybrid-initSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 4 are distinctive, and 10 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Test a model end-to-end using the xybrid execution system.
- Very specific: line 16
If $ARGUMENTS is provided, use it to find the model.
- Distinctive: line 18
Search for the model in these locations (in order):
- Very specific: line 24
Verify that model_metadata.json exists in the model directory.
- Very specific: line 30
Read model_metadata.json and check:
- Distinctive: line 37
If any check fails, report the specific issue and suggest how to fix it.
- Very specific: line 59
Check for an existing example in crates/xybrid-core/examples/ that matches the model.
- Very specific: line 61
If no example exists, create a minimal one at crates/xybrid-core/examples/{model_id}_test.rs:
- Very specific: line 97
Run from the repos/xybrid/ directory (or the repo root if that's where Cargo.toml is):
- Distinctive: line 103
Add feature flags based on the model type (see table in Step 3).
- Distinctive: line 109
Check the output based on model type:
- Very specific: line 135
"model_metadata.json not found": Check the model directory path
- Very specific: line 140
"feature not enabled": Add the required feature flag (e.g.
- Very specific: line 141
"llm backend not available": Add --features llm-llamacpp for GGUF models
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill 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.
Files
Test a model end-to-end using the xybrid execution system.
The user should specify which model to test (e.g., "test kokoro-82m" or "test the TTS model").
Input: $ARGUMENTS (optional — model name or path to model directory)
Step 1: Locate the Model
If $ARGUMENTS is provided, use it to find the model. Otherwise ask which model to test.
Search for the model in these locations (in order):
- Direct path if
$ARGUMENTSis a directory path integration-tests/fixtures/models/{name}/~/.xybrid/cache/{name}/- Current directory
Verify that model_metadata.json exists in the model directory.
Step 2: Validate model_metadata.json
Read model_metadata.json and check:
- All files listed in
filesarray exist in the model directory model_fileinexecution_templatepoints to an actual file- JSON is valid and has required fields (
model_id,version,execution_template,files) - Preprocessing/postprocessing types are valid enum values
If any check fails, report the specific issue and suggest how to fix it.
Step 3: Determine Test Strategy
Based on the execution_template.type and metadata.task:
| Task | Input | Expected Output | Feature Flags |
text-to-speech | Envelope::Text("Hello world") | Audio bytes (length > 0) | default |
speech-recognition (Onnx) | Envelope::Audio(wav_bytes) | Text transcription | default |
speech-recognition (GgmlWhisper) | Envelope::Audio(wav_bytes) | Text transcription | asr-whispercpp (in every platform-* preset) |
speech-recognition (SafeTensors) | Envelope::Audio(wav_bytes) | Text transcription | candle,candle-metal — opt-in only; no preset enables Candle |
text-generation (Gguf) | Envelope::Text("Hello") | Text response | llm-llamacpp |
text-embedding | Envelope::Text("test sentence") | Embedding vector (f32) | default |
image_classification | Raw image bytes | Class probabilities | default |
Step 4: Find or Create Test Example
Check for an existing example in crates/xybrid-core/examples/ that matches the model.
If no example exists, create a minimal one at crates/xybrid-core/examples/{model_id}_test.rs:
//! Test example for {model_id}
use std::collections::HashMap;
use std::path::PathBuf;
use xybrid_core::execution::{ModelMetadata, TemplateExecutor};
use xybrid_core::ir::{Envelope, EnvelopeKind};
fn main() -> Result<(), Box<dyn std::error::Error>> {
let model_dir = PathBuf::from("integration-tests/fixtures/models/{model_id}");
let metadata_path = model_dir.join("model_metadata.json");
let metadata: ModelMetadata = serde_json::from_str(&std::fs::read_to_string(&metadata_path)?)?;
let mut executor = TemplateExecutor::with_base_path(model_dir.to_str().unwrap());
// Create appropriate input based on model task
let input = Envelope {
kind: EnvelopeKind::Text("Hello world".into()), // adjust per task
metadata: HashMap::new(),
};
// Third arg is an optional `&GenerationConfig` override.
let output = executor.execute(&metadata, &input, None)?;
println!("Output: {:?}", output.kind);
println!("Test passed!");
Ok(())
}Adjust the input type based on the model task (Text for TTS/LLM/embedding, Audio for ASR).
Step 5: Run the Test
Run from the repos/xybrid/ directory (or the repo root if that's where Cargo.toml is):
cargo run --example {example_name} -p xybrid-core --features {features}Add feature flags based on the model type (see table in Step 3).
Step 6: Validate Output
Check the output based on model type:
- TTS: Output should be
EnvelopeKind::Audio(bytes)withbytes.len() > 0. Optionally save tooutput.wavfor manual listening. - ASR: Output should be
EnvelopeKind::Text(transcription)with non-empty text. - LLM: Output should be
EnvelopeKind::Text(response)with non-empty text. - Embedding: Output should be
EnvelopeKind::Embedding(vec)with expected dimensionality. - Classification: Output should contain class probabilities or indices.
Step 7: Report Results
Print a summary:
Model: {model_id}
Task: {task}
Input: {input_type}
Output: {output_summary}
Status: PASS / FAIL
{If FAIL: specific error message and suggestion}Common Issues
- "model_metadata.json not found": Check the model directory path
- "file not found": A file listed in
filesarray doesn't exist — download it or fix the path - "preprocessing failed": Wrong preprocessing step for the model type
- "ONNX error": Model file may be corrupted or wrong format
- "SafeTensors execution requires the 'candle' feature": the bundle is a Candle/SafeTensors model and no
platform-*preset enables Candle any more. Either add--features candleexplicitly, or switch to the GGML bundle (ExecutionTemplate::GgmlWhisper) that runs onasr-whispercpp— e.g.whisper-tiny-ggmlinstead ofwhisper-tiny. - "feature not enabled": Add the required feature flag (e.g.
--features asr-whispercppfor GGML Whisper,--features candlefor SafeTensors) - "llm backend not available": Add
--features llm-llamacppfor GGUF models
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
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.

