Automated summary
An advanced guide for migrating recruiting data (LinkedIn Recruiter, Greenhouse, Lever, custom ATS, CSV) into Juicebox, covering source assessment, schema mapping, and record transformation.
Strengths
- Includes a source assessment script (duplicates, field coverage, quality score, estimated migration time) to run before migrating
- Provides a comparison table of sources with their complexity and typical pitfalls
- Offers a reusable SchemaMapper class with declarative field mappings, transforms, and null handling
- Addresses bulk imports via the Enterprise plan and includes kubectl/curl execution access
Limitations
- The available content stops at schema mapping: load, post-migration validation, and rollback steps are not covered
- Assumes source data access and a Juicebox Enterprise plan for bulk imports
- Examples are LinkedIn- and TypeScript-specific, with limited guidance for custom ATS sources
Use it when planning a recruiting data migration into Juicebox and you need to assess the source, define field mappings, and transform records.
Avoid it if you need documentation on day-to-day Juicebox usage or you lack access to source data exports.
Security analysis
CautionThe content contains no destructive commands, no curl|sh piping, no base64 payloads, and no attempts to exfiltrate secrets or disable safety controls — it is ordinary TypeScript migration scaffolding. The risk is elevated only to 'caution' because it grants broad shell/network and cluster access for legitimate bulk-migration purposes and processes large volumes of personal data without any privacy or rollback safeguards.
- •Declares broad Bash(kubectl:*) and Bash(curl:*) permissions; while plausible for migration/import work, unrestricted curl allows arbitrary outbound network requests and kubectl allows cluster-wide actions with no scoping in the instructions.
- •Skill handles sensitive PII (emails, names, phone numbers, LinkedIn profile URLs) at scale with no guidance on consent, retention, encryption, or where that data may be transmitted.
- •Includes Write/Edit with no guardrails or backup/rollback instructions before bulk import operations that could overwrite existing records.
Examples
I need to migrate our LinkedIn Recruiter exports into Juicebox. Can you assess the sample CSV I've placed in ./data and tell me the field coverage, duplicate rate, and estimated migration time?Create a SchemaMapper for our Greenhouse export mapping into Juicebox, including a location normalizer and a required/optional flag for each field.Our homegrown ATS exports JSON with nested candidate objects. Help me write a transformation pipeline to flatten and map it into Juicebox, then run a dry-run bulk import.name: juicebox-migration-deep-dive description: | Advanced Juicebox data migration strategies. Use when migrating from other recruiting platforms, performing bulk data imports, or implementing complex data transformation pipelines. Trigger with phrases like "juicebox data migration", "migrate to juicebox", "juicebox import", "juicebox bulk migration". allowed-tools: Read, Write, Edit, Bash(kubectl:), Bash(curl:) version: 1.0.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io
Juicebox Migration Deep Dive
Overview
Advanced strategies for migrating data to Juicebox from other recruiting and people search platforms.
Prerequisites
- Source data access and export capabilities
- Juicebox Enterprise plan (for bulk imports)
- Data mapping documentation
- Testing environment
Migration Sources
| Source | Complexity | Common Issues | |--------|------------|---------------| | LinkedIn Recruiter | Medium | Rate limits, field mapping | | Greenhouse | Low | Well-documented API | | Lever | Low | Standard export format | | Custom ATS | High | Custom transformation needed | | CSV/Excel | Low | Data quality issues |
Instructions
Step 1: Data Assessment
// scripts/assess-source-data.ts
interface DataAssessment {
totalRecords: number;
uniqueProfiles: number;
duplicates: number;
fieldCoverage: Record<string, number>;
dataQualityScore: number;
estimatedMigrationTime: string;
}
export async function assessSourceData(
source: string,
sampleSize: number = 1000
): Promise<DataAssessment> {
const sample = await loadSampleData(source, sampleSize);
const assessment: DataAssessment = {
totalRecords: sample.total,
uniqueProfiles: new Set(sample.records.map(r => r.email)).size,
duplicates: sample.total - new Set(sample.records.map(r => r.email)).size,
fieldCoverage: calculateFieldCoverage(sample.records),
dataQualityScore: calculateQualityScore(sample.records),
estimatedMigrationTime: estimateMigrationTime(sample.total)
};
return assessment;
}
function calculateFieldCoverage(records: any[]): Record<string, number> {
const fields = ['name', 'email', 'title', 'company', 'location', 'phone'];
const coverage: Record<string, number> = {};
for (const field of fields) {
const count = records.filter(r => r[field] && r[field].trim()).length;
coverage[field] = (count / records.length) * 100;
}
return coverage;
}
Step 2: Schema Mapping
// lib/migration/schema-mapper.ts
export interface FieldMapping {
sourceField: string;
targetField: string;
transform?: (value: any) => any;
required: boolean;
}
export const linkedInMapping: FieldMapping[] = [
{ sourceField: 'firstName', targetField: 'first_name', required: true },
{ sourceField: 'lastName', targetField: 'last_name', required: true },
{
sourceField: 'fullName',
targetField: 'name',
transform: (v) => v || undefined,
required: false
},
{ sourceField: 'headline', targetField: 'title', required: false },
{ sourceField: 'companyName', targetField: 'company', required: false },
{
sourceField: 'location',
targetField: 'location',
transform: normalizeLocation,
required: false
},
{
sourceField: 'profileUrl',
targetField: 'linkedin_url',
transform: normalizeLinkedInUrl,
required: false
},
{
sourceField: 'connectionDegree',
targetField: 'metadata.connection_degree',
required: false
}
];
export class SchemaMapper {
constructor(private mappings: FieldMapping[]) {}
mapRecord(source: Record<string, any>): Record<string, any> {
const target: Record<string, any> = {};
for (const mapping of this.mappings) {
let value = this.getNestedValue(source, mapping.sourceField);
if (mapping.transform) {
value = mapping.transform(value);
}
if (value !== undefined && value !== null && value !== '') {
this.setNestedValue(target, mapping.targetField, value);
} else if (mapping.required) {
throw new Error(`Required field missing: ${mapping.sourceField}`);
}
}
return target;
}
}
Step 3: Data Transformation Pipeline
// lib/migration/pipeline.ts
import { Transform, pipeline } from 'stream';
import { promisify } from 'util';
const pipelineAsync = promisify(pipeline);
export class MigrationPipeline {
private stages: Transform[] = [];
addStage(name: string, transform: (record: any) => any): this {
this.stages.push(new Transform({
objectMode: true,
transform(record, encoding, callback) {
try {
const result = transform(record);
if (result) {
this.push(result);
}
callback();
} catch (error) {
callback(error as Error);
}
}
}));
return this;
}
async run(source: Readable, destination: Writable): Promise<MigrationStats> {
const stats = new MigrationStats();
const statsTracker = new Transform({
objectMode: true,
transform(record, encoding, callback) {
stats.increment();
this.push(record);
callback();
}
});
await pipelineAsync(
source,
...this.stages,
statsTracker,
destination
);
return stats;
}
}
// Usage
const pipeline = new MigrationPipeline()
.addStage('parse', parseCSVRecord)
.addStage('validate', validateRecord)
.addStage('deduplicate', deduplicateRecord)
.addStage('transform', transformToJuiceboxSchema)
.addStage('enrich', enrichWithMetadata);
Step 4: Bulk Import with Rate Limiting
// lib/migration/bulk-importer.ts
export class BulkImporter {
private rateLimiter: RateLimiter;
private batchSize: number;
private maxConcurrent: number;
constructor(options: {
requestsPerSecond: number;
batchSize: number;
maxConcurrent: number;
}) {
this.rateLimiter = new RateLimiter(options.requestsPerSecond);
this.batchSize = options.batchSize;
this.maxConcurrent = options.maxConcurrent;
}
async import(records: Profile[]): Promise<ImportResult> {
const result: ImportResult = {
total: records.length,
successful: 0,
failed: 0,
errors: []
};
// Split into batches
const batches = chunk(records, this.batchSize);
// Process batches with concurrency limit
const semaphore = new Semaphore(this.maxConcurrent);
await Promise.all(batches.map(async (batch, index) => {
await semaphore.acquire();
try {
await this.rateLimiter.wait();
const batchResult = await this.importBatch(batch);
result.successful += batchResult.successful;
result.failed += batchResult.failed;
result.errors.push(...batchResult.errors);
logger.info(`Batch ${index + 1}/${batches.length} complete`, {
successful: batchResult.successful,
failed: batchResult.failed
});
} finally {
semaphore.release();
}
}));
return result;
}
private async importBatch(batch: Profile[]): Promise<BatchResult> {
try {
const response = await juiceboxClient.profiles.bulkImport(batch);
return {
successful: response.created + response.updated,
failed: response.failed,
errors: response.errors
};
} catch (error) {
return {
successful: 0,
failed: batch.length,
errors: [{ message: (error as Error).message, records: batch }]
};
}
}
}
Step 5: Validation and Reconciliation
// lib/migration/validator.ts
export class MigrationValidator {
async validateMigration(
sourceCount: number,
destinationQuery: string
): Promise<ValidationReport> {
const report: ValidationReport = {
sourceCount,
destinationCount: 0,
matchRate: 0,
missingRecords: [],
dataIntegrityIssues: []
};
// Count destination records
const destResult = await juiceboxClient.search.people({
query: destinationQuery,
limit: 0
});
report.destinationCount = destResult.total;
report.matchRate = (report.destinationCount / sourceCount) * 100;
// Sample validation
const sampleSize = Math.min(100, sourceCount);
const sample = await this.getSampleFromSource(sampleSize);
for (const record of sample) {
const match = await this.findInDestination(record);
if (!match) {
report.missingRecords.push(record.id);
} else {
const issues = this.compareRecords(record, match);
if (issues.length > 0) {
report.dataIntegrityIssues.push({
recordId: record.id,
issues
});
}
}
}
return report;
}
private compareRecords(source: any, dest: any): string[] {
const issues: string[] = [];
const criticalFields = ['name', 'email', 'company'];
for (const field of criticalFields) {
if (source[field] !== dest[field]) {
issues.push(`${field} mismatch: "${source[field]}" vs "${dest[field]}"`);
}
}
return issues;
}
}
Step 6: Rollback Strategy
// lib/migration/rollback.ts
export class MigrationRollback {
private checkpointFile: string;
constructor(migrationId: string) {
this.checkpointFile = `./checkpoints/${migrationId}.json`;
}
async saveCheckpoint(state: MigrationState): Promise<void> {
await fs.writeFile(this.checkpointFile, JSON.stringify(state, null, 2));
}
async loadCheckpoint(): Promise<MigrationState | null> {
try {
const data = await fs.readFile(this.checkpointFile, 'utf-8');
return JSON.parse(data);
} catch {
return null;
}
}
async rollback(migrationId: string): Promise<RollbackResult> {
const checkpoint = await this.loadCheckpoint();
if (!checkpoint) {
throw new Error('No checkpoint found for rollback');
}
// Delete imported records
const deleted = await juiceboxClient.profiles.bulkDelete({
filter: { migrationId }
});
return {
recordsRolledBack: deleted.count,
checkpoint: checkpoint.lastProcessedId
};
}
}
Migration Checklist
## Pre-Migration
- [ ] Source data exported and validated
- [ ] Field mapping documented
- [ ] Test migration on sample data
- [ ] Rollback plan documented
- [ ] Stakeholder sign-off
## During Migration
- [ ] Monitoring dashboards active
- [ ] Progress tracking enabled
- [ ] Error logging configured
- [ ] Checkpoint saves working
## Post-Migration
- [ ] Reconciliation complete
- [ ] Data integrity verified
- [ ] Source system archived
- [ ] Documentation updated
- [ ] Team training complete
Output
- Data assessment tools
- Schema mapping configuration
- Transformation pipeline
- Bulk import with rate limiting
- Validation and reconciliation
Resources
Summary
This skill pack completes the enterprise-grade Juicebox integration toolkit.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/advanced-juicebox-data-migration-mm5t8c2m/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/advanced-juicebox-data-migration-mm5t8c2m' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/advanced-juicebox-data-migration-mm5t8c2m/download' --output '.skill-downloads/advanced-juicebox-data-migration-mm5t8c2m/SKILL.md.part' && mv '.skill-downloads/advanced-juicebox-data-migration-mm5t8c2m/SKILL.md.part' '.skill-downloads/advanced-juicebox-data-migration-mm5t8c2m/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Write, Edit, Bash(kubectl:*), Bash(curl:*)
Original excerpt: Prerequisites
- Source data access and export capabilities
- Juicebox Enterprise plan (for bulk imports)
- Data mapping documentation
- Testing environment
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/advanced-juicebox-data-migration-mm5t8c2m/SKILL.md' && test -s '.skill-downloads/advanced-juicebox-data-migration-mm5t8c2m/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/juicebox-migration-deep-dive' && cp -R '.skill-downloads/advanced-juicebox-data-migration-mm5t8c2m' '.claude/skills/juicebox-migration-deep-dive'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/advanced-juicebox-data-migration-mm5t8c2m'openskills read 'advanced-juicebox-data-migration-mm5t8c2m'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/advanced-juicebox-data-migration-mm5t8c2m/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Create Interactive Maps with kepler.gl
Data & AI
Create interactive map visualizations and export standalone HTML using the keplergl Python package. Use to plot geospatial data from DataFrames, GeoJSON, or CSV.
Agent-Driven Parameter Optimization
Data & AI
Guide for optimizing configurable systems with a measurable objective, using bounded trials and evidence-based recommendations.
ICP Visitor Outreach
Data & AI
Identify signed-up users matching the ideal customer profile but stalled, and draft personalized outreach to re-engage them.