juicebox-migration-deep-dive
A guide for migrating recruiting data and workflows to Juicebox, covering query translation and ATS setup.
Install
mkdir -p .claude/skills/juicebox-migration-deep-dive && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/8988" && unzip -o skill.zip -d .claude/skills/juicebox-migration-deep-dive && rm skill.zipInstalls to .claude/skills/juicebox-migration-deep-dive
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Migrate to Juicebox from other tools.Key capabilities
- →Translate boolean search strings to natural language
- →Migrate saved searches to Juicebox
- →Configure ATS integrations
- →Set up outreach sequences
How it works
It maps legacy boolean search logic to natural language queries compatible with PeopleGPT and facilitates the migration of talent pools and ATS connections.
Inputs & outputs
When to use juicebox-migration-deep-dive
- →Converting boolean search strings for PeopleGPT
- →Migrating saved searches to Juicebox
- →Configuring ATS integrations for talent pools
- →Setting up outreach sequences during migration
About this skill
Juicebox Migration Deep Dive
Comparison
| Feature | LinkedIn Recruiter | Juicebox |
|---|---|---|
| Search | Boolean only | Natural language (PeopleGPT) |
| Contact data | InMail only | Email + phone |
| ATS integration | Limited | 41+ systems |
| AI features | Basic | AI Skills Map, research profiles |
Migration Steps
- Export saved searches from current tool
- Translate boolean queries to natural language
- Re-create talent pools in Juicebox
- Configure ATS integration
- Set up outreach sequences
Query Translation
# Boolean: ("software engineer" OR "SWE") AND "Python" AND "San Francisco"
# PeopleGPT: software engineer with Python experience in San Francisco
Overview
This migration workflow moves approved enrichment configurations without treating contact records as transferable test data. Every cohort retains source authority, suppression, retention, destination, and rollback boundaries.
Prerequisites
- A signed migration plan with data owners, source-authority and suppression policies, synthetic fixtures, approved destination, and cutover/rollback owner.
Instructions
- Baseline source authority, aggregate counts, suppression state, retention, destination scope, and synthetic probe outcomes before migration.
- Rehearse a bounded idempotent migration in sandbox; quarantine unknown sources, schema mismatches, and unverified records.
- Migrate one approved cohort at a time, compare aggregate counts/policy probes, and retain opaque correlation IDs only.
- Cut over after owner approval and an observation window; keep the prior configuration available until recovery criteria are met.
- Roll back for source, destination, suppression, integrity, or retention failure and delete staged artifacts before retrying.
Output
Create a migration receipt with cohort, baseline/target counts, source/destination/suppression results, checkpoint, owner approval, cutover status, retention/deletion action, and rollback reference. Never attach contact details or credentials.
Error Handling
Stop on unknown authority, destination, suppression state, incomplete deletion, or non-idempotent replay. Restore the prior controlled path and escalate with redacted evidence rather than forcing cutover.
Examples
cohort=synthetic-prospects-01; baseline=420; migrated=420; source=approved; suppression=pass; contacts_exported=0; cutover=held; rollback=old-client-r8 documents a safe rehearsal.
Resources
- PeopleGPT Guide
Next Steps
Start with juicebox-install-auth.
When not to use it
- →When migrating to platforms other than Juicebox
How it compares
It provides a structured translation path for boolean-based search workflows to AI-driven natural language search.
Compared to similar skills
juicebox-migration-deep-dive side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| juicebox-migration-deep-dive (this skill) | 0 | 2mo | No flags | Beginner |
| identify-vault-protocol | 1 | 8mo | No flags | Intermediate |
| openevidence-core-workflow-a | 1 | 2mo | Review | Intermediate |
| biopython | 1 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
identify-vault-protocol
tradingstrategy-ai
Identify an unknown vault protocol based on its smart contract address
openevidence-core-workflow-a
jeremylongshore
Execute OpenEvidence clinical query workflow for point-of-care decisions. Use when implementing real-time clinical decision support, building EHR-integrated evidence lookups, or point-of-care queries. Trigger with phrases like "openevidence clinical query", "point of care", "quick clinical lookup", "evidence search".
biopython
davila7
Primary Python toolkit for molecular biology. Preferred for Python-based PubMed/NCBI queries (Bio.Entrez), sequence manipulation, file parsing (FASTA, GenBank, FASTQ, PDB), advanced BLAST workflows, structures, phylogenetics. For quick BLAST, use gget. For direct REST API, use pubmed-database.
reference-sdk
parcadei
Check reference SDK implementations using btca ask
apollo-hello-world
jeremylongshore
Create a minimal working Apollo.io example. Use when starting a new Apollo integration, testing your setup, or learning basic Apollo API patterns. Trigger with phrases like "apollo hello world", "apollo example", "apollo quick start", "simple apollo code", "test apollo api".
evernote-core-workflow-b
jeremylongshore
Execute Evernote secondary workflow: Search and Retrieval. Use when implementing search features, finding notes, filtering content, or building search interfaces. Trigger with phrases like "search evernote", "find evernote notes", "evernote search", "query evernote".