Skip to content
Back to skills

2860 Quickstart Langgraph 91ad62a4

BSecurity

This guide gets you testing your LangGraph agent in **5 minutes**.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
code-qualitypythonbashtestingdebuggingapici/cdperformance

Works with

  • api

Security analysis

B84/100
  • mediumUses curl or wget to download content
  • criticalExfiltrates credentials via HTTP — exact pattern from Snyk ToxicSkills study

Pro shows the line behind each finding and how to fix it

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 2860-quickstart_langgraph_91ad62a4 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 2860 Quickstart Langgraph 91ad62a4?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 2860 Quickstart Langgraph 91ad62a4
[![Security: B — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-2860-quickstart-langgraph-91ad62a4/badge)](https://www.skillsdirectory.com/skills/tools-only-2860-quickstart-langgraph-91ad62a4)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
# Quick Start: Testing LangGraph with EvalView

This guide gets you testing your LangGraph agent in **5 minutes**.

## Step 1: Start Your LangGraph Agent

```bash
# Navigate to your LangGraph project
cd /path/to/your/langgraph-agent

# Start the server (check your project's README for the exact command)
python main.py
# OR
uvicorn main:app --reload --port 8000

# Verify it's running:
curl http://localhost:8000
```

## Step 2: Connect EvalView to Your Agent

```bash
# Auto-detect and configure the endpoint
evalview connect

# Or manually specify your endpoint:
evalview connect --endpoint http://localhost:8000/api/chat
```

This will:
- ✅ Test the connection
- ✅ Auto-update `.evalview/config.yaml`
- ✅ Tell you the correct adapter type

## Step 3: Run Your Tests

```bash
# Run with verbose output to see what's happening
evalview run --verbose
```

## Step 4: Review Results

After running tests, you'll see:
- ✅ Pass/fail status for each test
- 📊 Scores, costs, and latency
- 💾 Results saved to `.evalview/results/`

View detailed report:
```bash
evalview report .evalview/results/LATEST.json --detailed
```

## Troubleshooting

### "Cannot connect to agent"
```bash
# Check if your agent is running
curl -X POST http://localhost:8000/api/chat \
  -H "Content-Type: application/json" \
  -d '{"query": "test"}'

# If not working, check:
# 1. Is the server running?
# 2. Is it on port 8000?
# 3. What's the correct endpoint path?
```

### "Wrong endpoint"
Update `.evalview/config.yaml`:
```yaml
endpoint: http://localhost:YOUR_PORT/YOUR_PATH
```

### "Tool names don't match"
Run with `--verbose` to see the actual API response, then update your test YAML files with the correct tool names.

## Next Steps

1. **Customize test cases** in `tests/test-cases/`
2. **Add more scenarios** - Copy and modify the example YAMLs
3. **Adjust thresholds** - Based on your agent's actual performance
4. **Run regularly** - Add to your CI/CD pipeline

## Example Test Case

Create `tests/test-cases/my-test.yaml`:

```yaml
name: "My Custom Test"
description: "Test my agent does X"

input:
  query: "Your test query here"
  context: {}

expected:
  tools: []  # Add tool names after seeing verbose output
  output:
    contains:
      - "expected keyword 1"
      - "expected keyword 2"
    not_contains:
      - "error"

thresholds:
  min_score: 70
  max_cost: 0.50
  max_latency: 10000
```

## Tips

- 🔍 Always use `--verbose` initially to understand API responses
- 📝 Start with loose thresholds, tighten based on actual performance
- 🧪 Test one scenario at a time when debugging
- 💰 Set `OPENAI_API_KEY` in `.env.local` for LLM-as-judge evaluation

---

**Need help?** Check [DEBUGGING.md](DEBUGGING.md) or open an issue!

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.