juicebox-reference-architecture
Implement Juicebox reference architecture. Trigger: "juicebox architecture", "recruiting platform design".
Best use case
juicebox-reference-architecture is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Implement Juicebox reference architecture. Trigger: "juicebox architecture", "recruiting platform design".
Teams using juicebox-reference-architecture should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/juicebox-reference-architecture/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How juicebox-reference-architecture Compares
| Feature / Agent | juicebox-reference-architecture | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Implement Juicebox reference architecture. Trigger: "juicebox architecture", "recruiting platform design".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Juicebox Reference Architecture
## Overview
Production architecture for AI-powered candidate analysis integrations with Juicebox. Designed for recruiting teams needing automated dataset ingestion from job descriptions, intelligent candidate scoring and ranking, result caching for repeated searches, and seamless export to ATS platforms like Greenhouse and Lever. Key design drivers: search result freshness, candidate deduplication across sources, outreach sequencing, and analysis pipeline throughput for high-volume hiring.
## Architecture Diagram
```
Recruiter Dashboard ──→ Search Service ──→ Cache (Redis) ──→ Juicebox API
↓ /search
Queue (Bull) ──→ Analysis Worker /profiles
↓ /outreach
ATS Export Service ──→ Greenhouse/Lever
↓
Webhook Handler ←── Juicebox Events
```
## Service Layer
```typescript
class CandidateSearchService {
constructor(private juicebox: JuiceboxClient, private cache: CacheLayer) {}
async findAndRank(criteria: SearchCriteria): Promise<RankedCandidate[]> {
const cacheKey = `search:${this.hashCriteria(criteria)}`;
const cached = await this.cache.get(cacheKey);
if (cached) return cached;
const results = await this.juicebox.search(criteria);
const ranked = results.profiles.map(p => ({ ...p, score: this.scoreCandidate(p, criteria) }))
.sort((a, b) => b.score - a.score);
await this.cache.set(cacheKey, ranked, CACHE_CONFIG.searchResults.ttl);
return ranked;
}
async exportToATS(candidates: string[], jobId: string, ats: 'greenhouse' | 'lever'): Promise<ExportResult> {
const deduped = await this.deduplicateAgainstATS(candidates, jobId, ats);
return this.juicebox.export({ profiles: deduped, destination: ats, job_id: jobId });
}
}
```
## Caching Strategy
```typescript
const CACHE_CONFIG = {
searchResults: { ttl: 1800, prefix: 'search' }, // 30 min — candidate pools shift slowly
profiles: { ttl: 3600, prefix: 'profile' }, // 1 hr — profile data stable short-term
analysisRuns: { ttl: 7200, prefix: 'analysis' }, // 2 hr — analysis results are expensive to recompute
atsState: { ttl: 300, prefix: 'ats' }, // 5 min — ATS pipeline freshness for dedup
outreach: { ttl: 60, prefix: 'outreach' }, // 1 min — sequence status changes frequently
};
// New search invalidates matching cached results; ATS export clears ats cache for that job
```
## Event Pipeline
```typescript
class RecruitingPipeline {
private queue = new Bull('juicebox-events', { redis: process.env.REDIS_URL });
async onSearchComplete(searchId: string, results: RankedCandidate[]): Promise<void> {
await this.queue.add('analyze', { searchId, candidateIds: results.map(r => r.id) },
{ attempts: 3, backoff: { type: 'exponential', delay: 2000 } });
}
async processOutreachEvent(event: OutreachEvent): Promise<void> {
if (event.type === 'reply_received') await this.flagForRecruiterReview(event);
if (event.type === 'bounced') await this.markInvalid(event.candidateId);
await this.syncStatusToATS(event);
}
}
```
## Data Model
```typescript
interface SearchCriteria { role: string; skills: string[]; location?: string; experienceYears?: number; companySize?: string; }
interface RankedCandidate { id: string; name: string; title: string; company: string; score: number; skills: string[]; profileUrl: string; }
interface OutreachSequence { id: string; candidateId: string; jobId: string; steps: OutreachStep[]; status: 'active' | 'replied' | 'bounced' | 'opted-out'; }
interface ExportResult { exported: number; duplicatesSkipped: number; atsJobId: string; }
```
## Scaling Considerations
- Parallelize search requests across role categories — Juicebox API supports concurrent queries
- Cache analysis results aggressively — AI scoring is the most expensive operation per candidate
- Batch ATS exports by job requisition to minimize Greenhouse/Lever API round-trips
- Deduplicate candidates across searches before outreach to avoid double-contacting
- Rate-limit outreach sequencing to maintain sender reputation and deliverability
## Error Handling
| Component | Failure Mode | Recovery |
|-----------|-------------|----------|
| Candidate search | Juicebox API timeout | Retry with reduced result count, serve cached results if available |
| Analysis pipeline | Scoring model latency spike | Queue with timeout, return unscored results with flag |
| ATS export | Greenhouse rate limit | Batch retry with exponential backoff, notify recruiter on persistent failure |
| Outreach sequence | Email bounce | Mark candidate invalid, remove from active sequences, update ATS |
| Webhook handler | Duplicate event delivery | Idempotency key on event ID + candidate ID |
## Resources
- [Juicebox AI](https://juicebox.ai)
- [Juicebox Integrations](https://juicebox.ai/integrations)
## Next Steps
See `juicebox-deploy-integration`.Related Skills
workhuman-reference-architecture
Workhuman reference architecture for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman reference architecture".
wispr-reference-architecture
Wispr Flow reference architecture for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr reference architecture".
windsurf-reference-architecture
Implement Windsurf reference architecture with optimal project structure and AI configuration. Use when designing workspace configuration for Windsurf, setting up team standards, or establishing architecture patterns that maximize Cascade effectiveness. Trigger with phrases like "windsurf architecture", "windsurf project structure", "windsurf best practices", "windsurf team setup", "optimize for cascade".
windsurf-architecture-variants
Choose workspace architectures for different project scales in Windsurf. Use when deciding how to structure Windsurf workspaces for monorepos, multi-service setups, or polyglot codebases. Trigger with phrases like "windsurf workspace strategy", "windsurf monorepo", "windsurf project layout", "windsurf multi-service", "windsurf workspace size".
webflow-reference-architecture
Implement Webflow reference architecture — layered project structure, client wrapper, CMS sync service, webhook handlers, and caching layer for production integrations. Trigger with phrases like "webflow architecture", "webflow project structure", "how to organize webflow", "webflow integration design", "webflow best practices".
vercel-reference-architecture
Implement a Vercel reference architecture with layered project structure and best practices. Use when designing new Vercel projects, reviewing project structure, or establishing architecture standards for Vercel applications. Trigger with phrases like "vercel architecture", "vercel project structure", "vercel best practices layout", "how to organize vercel project".
vercel-architecture-variants
Choose and implement Vercel architecture blueprints for different scales and use cases. Use when designing new Vercel projects, choosing between static, serverless, and edge architectures, or planning how to structure a multi-project Vercel deployment. Trigger with phrases like "vercel architecture", "vercel blueprint", "how to structure vercel", "vercel monorepo", "vercel multi-project".
veeva-reference-architecture
Veeva Vault reference architecture for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva reference architecture".
vastai-reference-architecture
Implement Vast.ai reference architecture for GPU compute workflows. Use when designing ML training pipelines, structuring GPU orchestration, or establishing architecture patterns for Vast.ai applications. Trigger with phrases like "vastai architecture", "vastai design pattern", "vastai project structure", "vastai ml pipeline".
twinmind-reference-architecture
Production architecture for meeting AI systems using TwinMind: transcription pipeline, memory vault, action item workflow, and calendar integration. Use when implementing reference architecture, or managing TwinMind meeting AI operations. Trigger with phrases like "twinmind reference architecture", "twinmind reference architecture".
together-reference-architecture
Together AI reference architecture for inference, fine-tuning, and model deployment. Use when working with Together AI's OpenAI-compatible API. Trigger: "together reference architecture".
techsmith-reference-architecture
TechSmith reference architecture for Snagit COM API and Camtasia automation. Use when working with TechSmith screen capture and video editing automation. Trigger: "techsmith reference architecture".