What's Missing in Standard WorkOS Architecture
WorkOS creates user sessions, but lacks the infrastructure to detect when users first achieve value in your application.
Standard WorkOS Flow vs Optimized Skene Flow
Standard Flow
1
User signs up via WorkOS
2
User record created but no activation tracking
3
No automatic trigger for activation milestones
Skene Flow
1
Watch WorkOS user events for signup and first actions
2
Detect when user completes first value milestone
3
Trigger activation email sequence with personalized onboarding
4
Track activation completion and send milestone emails
Visual comparison of the flows:
Loading diagram...
How Skene Fixes This
This Skene configuration watches WorkOS user events and detects activation milestones. When users achieve their first value moment, it triggers personalized onboarding emails and feature discovery guides.
Implementation Comparison
Using Skene Infrastructure
Auto-managed state. Installed via Prompt.
Install via Prompt
cursor.mdc
@task: Initialize Skene.
@action: Analyze my local code, validating subscription via `npx skene login`, and generate `skene.config.ts` to implement the Activation Loop pattern for WorkOS.Copy Skene Prompt for Cursor
Generated skene.config.ts
skene.config.ts
// skene.config.ts - The Automated Way
import { defineLoop } from '@skene/sdk';
export default defineLoop({
type: 'activation',
opinion: 'Detect when users complete their first key action and trigger personalized onboarding',
steps: [
{
trigger: {
type: 'database',
table: 'users',
event: 'insert'
},
condition: {
type: 'query',
query: `SELECT * FROM user_actions WHERE user_id = $1 AND action_type = 'first_project_created'`,
timeout: '5m'
},
action: {
type: 'email',
provider: 'resend',
template: 'activation_welcome',
personalization: {
name: '{{user.name}}',
activationLink: '{{user.activation_link}}'
}
}
}
],
recovery: {
retries: 3,
backoff: 'exponential'
}
});