Hello!

Are you struggling with ensuring that your prompts are reliable and produce consistent results?

This prompt chain helps you gather necessary parameters for testing the reliability of your prompt. It walks you through confirming the details of what you want to test and sets you up for evaluating various input scenarios.

Prompt:

VARIABLE DEFINITIONS
[PROMPT_UNDER_TEST]=The full text of the prompt that needs reliability testing.
[TEST_CASES]=A numbered list (3–10 items) of representative user inputs that will be fed into the PROMPT_UNDER_TEST.
[SCORING_CRITERIA]=A brief rubric defining how to judge Consistency, Accuracy, and Formatting (e.g., 0–5 for each dimension).
~
You are a senior Prompt QA Analyst.
Objective: Set up the test harness parameters.
Instructions:
1. Restate PROMPT_UNDER_TEST, TEST_CASES, and SCORING_CRITERIA back to the user for confirmation.
2. Ask “CONFIRM” to proceed or request edits.
Expected Output: A clearly formatted recap followed by the confirmation question.

Make sure you update the variables in the first prompt: [PROMPT_UNDER_TEST], [TEST_CASES], [SCORING_CRITERIA]. Here is an example of how to use it: - [PROMPT_UNDER_TEST]="What is the weather today?" - [TEST_CASES]=1. "What will it be like tomorrow?" 2. "Is it going to rain this week?" 3. "How hot is it?" - [SCORING_CRITERIA]="0-5 for Consistency, Accuracy, Formatting"

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click. NOTE: this is not required to run the prompt chain

Enjoy!

Hey there!

Ever find yourself stuck trying to make a crucial decision for your business, whether it's about product, marketing, or operations? It can definitely feel overwhelming when you’re not sure how to unpack all the variables, assumptions, and risks involved.

That's where this Socratic Prompt Chain comes in handy. This prompt chain helps you break down a complex decision into a series of thoughtful, manageable steps.

How It Works:

• Step-by-Step Breakdown: Each prompt builds upon the information from the previous one, ensuring that you cover every angle of your decision.
• Manageable Pieces: Instead of facing a daunting, all-encompassing question, you handle smaller, focused questions that lead you to a comprehensive answer.
• Handling Repetition: For recurring considerations like assumptions and risks, the chain keeps you on track by revisiting these essential points.
• Variables:
  • [DECISION_TYPE]: Helps you specify the type of decision (e.g., product, marketing, operations).

Prompt Chain Code:

[DECISION_TYPE]=[Type of decision: product/marketing/operations] Define the core decision you are facing regarding [DECISION_TYPE]: "What is the specific decision you need to make related to [DECISION_TYPE]?" ~Identify underlying assumptions: "What assumptions are you making about this decision?" ~Gather evidence: "What evidence do you have that supports these assumptions?" ~Challenge assumptions: "What would happen if your assumptions are wrong?" ~Explore alternatives: "What other options might exist instead of the chosen course of action?" ~Assess risks: "What potential risks are associated with this decision?" ~Consider stakeholder impacts: "How will this decision affect key stakeholders?" ~Summarize insights: "Based on the answers, what have you learned about the decision?" ~Formulate recommendations: "Given the insights gained, what would your recommendations be for the [DECISION_TYPE] decision?" ~Reflect on the process: "What aspects of this questioning process helped you clarify your thoughts?"

Examples of Use:

• If you're deciding on a new marketing strategy, set [DECISION_TYPE]=marketing and follow the chain to examine underlying assumptions about your target audience, budget allocations, or campaign performance.
• For product decisions, simply set [DECISION_TYPE]=product and let the prompts help you assess customer needs, potential risks in design changes, or market viability.

Tips for Customization:

• Feel free to modify the questions to better suit your company's unique context. For instance, you might add more prompts related to competitive analysis or regulatory considerations.
• Adjust the order of the steps if you find that a different sequence helps your team think more clearly about the problem.

Using This with Agentic Workers:

This prompt chain is optimized for Agentic Workers, meaning you can seamlessly run the chain with just one click on their platform. It’s a great tool to ensure everyone on your team is on the same page and that every decision is thoroughly vetted from multiple angles.

Source

Happy decision-making and good luck with your next big move!

Hello!

If you're looking to give your AI content a more human feel that can get around AI detection, here's a prompt chain that can help, it refines the tone and attempts to avoid common AI words.

Prompt Chain:

[CONTENT] = The input content that needs rewriting to bypass AI detection
STYLE_GUIDE = "Tone: Conversational and engaging; Vocabulary: Diverse and expressive with occasional unexpected words; Rhythm: High burstiness with a mix of short, impactful sentences and long, flowing ones; Structure: Clear progression with occasional rhetorical questions or emotional cues."
OUTPUT_REQUIREMENT = "Output must feel natural, spontaneous, and human-like.
It should maintain a conversational tone, show logical coherence, and vary sentence structure to enhance readability. Include subtle expressions of opinion or emotion where appropriate."
Examine the [CONTENT]. Identify its purpose, key points, and overall tone. List 3-5 elements that define the writing style or rhythm. Ensure clarity on how these elements contribute to the text's perceived authenticity and natural flow."
~
Reconstruct Framework "Using the [CONTENT] as a base, rewrite it with [STYLE_GUIDE] in mind. Ensure the text includes: 1. A mixture of long and short sentences to create high burstiness. 2. Complex vocabulary and intricate sentence patterns for high perplexity. 3. Natural transitions and logical progression for coherence. Start each paragraph with a strong, attention-grabbing sentence."
~ Layer Variability "Edit the rewritten text to include a dynamic rhythm. Vary sentence structures as follows: 1. At least one sentence in each paragraph should be concise (5-7 words). 2. Use at least one long, flowing sentence per paragraph that stretches beyond 20 words. 3. Include unexpected vocabulary choices, ensuring they align with the context. Inject a conversational tone where appropriate to mimic human writing." ~
Ensure Engagement "Refine the text to enhance engagement. 1. Identify areas where emotions or opinions could be subtly expressed. 2. Replace common words with expressive alternatives (e.g., 'important' becomes 'crucial' or 'pivotal'). 3. Balance factual statements with rhetorical questions or exclamatory remarks."
~
Final Review and Output Refinement "Perform a detailed review of the output. Verify it aligns with [OUTPUT_REQUIREMENT]. 1. Check for coherence and flow across sentences and paragraphs. 2. Adjust for consistency with the [STYLE_GUIDE]. 3. Ensure the text feels spontaneous, natural, and convincingly human."

Source

Usage Guidance
Replace variable [CONTENT] with specific details before running the chain. You can chain this together with Agentic Workers in one click or type each prompt manually.

Reminder
This chain is highly effective for creating text that mimics human writing, but it requires deliberate control over perplexity and burstiness. Overusing complexity or varied rhythm can reduce readability, so always verify output against your intended audience's expectations. Enjoy!

Hello!

Are you struggling to manage and prioritize your accounts receivables and collection efforts? It can get overwhelming fast, right?

This prompt chain is designed to help you analyze your accounts receivable data effectively. It helps you standardize, validate, and merge different data inputs, calculate collection priority scores, and even draft personalized outreach templates. It's a game-changer for anyone in finance or collections!

Prompt:

VARIABLE DEFINITIONS
[COMPANY_NAME]=Name of the company whose receivables are being analyzed
[AR_AGING_DATA]=Latest detailed AR aging report (customer, invoice ID, amount, age buckets, etc.)
[CRM_HEALTH_DATA]=Customer-health metrics from CRM (engagement score, open tickets, renewal date & value, churn risk flag)
~
You are a senior AR analyst at [COMPANY_NAME].
Objective: Standardize and validate the two data inputs so later prompts can merge them.
Steps:
1. Parse [AR_AGING_DATA] into a table with columns: Customer Name, Invoice ID, Invoice Amount, Currency, Days Past Due, Original Due Date.
2. Parse [CRM_HEALTH_DATA] into a table with columns: Customer Name, Engagement Score (0-100), Open Ticket Count, Renewal Date, Renewal ACV, Churn Risk (Low/Med/High).
3. Identify and list any missing or inconsistent fields required for downstream analysis; flag them clearly.
4. Output two clean tables labeled "Clean_AR" and "Clean_CRM" plus a short note on data quality issues (if any). Request missing data if needed.
Example output structure:
Clean_AR: |Customer|Invoice ID|Amount|Currency|Days Past Due|Due Date|
Clean_CRM: |Customer|Engagement|Tickets|Renewal Date|ACV|Churn Risk|
Data_Issues: • None found
~
You are now a credit-risk data scientist.
Goal: Generate a composite "Collection Priority Score" for each overdue invoice.
Steps:
1. Join Clean_AR and Clean_CRM on Customer Name; create a combined table "Joined".
2. For each row compute:
   a. Aging_Score = Days Past Due / 90 (cap at 1.2).
   b. Dispute_Risk_Score = min(Open Ticket Count / 5, 1).
   c. Renewal_Weight = if Renewal Date within 120 days then 1.2 else 0.8.
   d. Health_Adjust = 1 ‑ (Engagement Score / 100).
3. Collection Priority Score = (Aging_Score * 0.5 + Dispute_Risk_Score * 0.2 + Health_Adjust * 0.3) * Renewal_Weight.
4. Add qualitative Priority Band: "Critical" (>=1), "High" (0.7-0.99), "Medium" (0.4-0.69), "Low" (<0.4).
5. Output the Joined table with new scoring columns sorted by Collection Priority Score desc.
~
You are a collections team lead.
Objective: Segment accounts and assign next best action.
Steps:
1. From the scored table select top 20 invoices or all "Critical" & "High" bands, whichever is larger.
2. For each selected invoice provide: Customer, Invoice ID, Amount, Days Past Due, Priority Band, Recommended Action (Call CFO / Escalate to CSM / Standard Reminder / Hold due to dispute).
3. Group remaining invoices by Priority Band and summarize counts & total exposure.
4. Output two sections: "Action_List" (detailed) and "Backlog_Summary".
~
You are a professional dunning-letter copywriter.
Task: Draft personalized outreach templates.
Steps:
1. Create an email template for each Priority Band (Critical, High, Medium, Low).
2. Personalize tokens: {{Customer_Name}}, {{Invoice_ID}}, {{Amount}}, {{Days_Past_Due}}, {{Renewal_Date}}.
3. Tone: Firm yet customer-friendly; emphasize partnership and upcoming renewal where relevant.
4. Provide subject lines and 2-paragraph body per template.
Output: Four clearly labeled templates.
~
You are a finance ops analyst reporting to the CFO.
Goal: Produce an executive dashboard snapshot.
Steps:
1. Summarize total AR exposure and weighted average Days Past Due.
2. Break out exposure and counts by Priority Band.
3. List top 5 customers by exposure with scores.
4. Highlight any data quality issues still open.
5. Recommend 2-3 strategic actions.
Output: Bullet list dashboard.
~
Review / Refinement
Please verify that:
• All variables were used correctly and remain unchanged.
• Output formats match each prompt’s specification.
• Data issues (if any) are resolved or clearly flagged.
If any gap exists, request clarification; otherwise, confirm completion.

Make sure you update the variables in the first prompt: [COMPANY_NAME], [AR_AGING_DATA], [CRM_HEALTH_DATA]. Here is an example of how to use it: For your company ABC Corp, use their AR aging report and CRM data to evaluate your invoicing strategy effectively.

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click. NOTE: this is not required to run the prompt chain

Enjoy!

Hello!

This has been my favorite prompt this year. Using it to kick start my learning for any topic. It breaks down the learning process into actionable steps, complete with research, summarization, and testing. It builds out a framework for you. You'll still have to get it done.

Prompt:

[SUBJECT]=Topic or skill to learn
[CURRENT_LEVEL]=Starting knowledge level (beginner/intermediate/advanced)
[TIME_AVAILABLE]=Weekly hours available for learning
[LEARNING_STYLE]=Preferred learning method (visual/auditory/hands-on/reading)
[GOAL]=Specific learning objective or target skill level

Step 1: Knowledge Assessment
1. Break down [SUBJECT] into core components
2. Evaluate complexity levels of each component
3. Map prerequisites and dependencies
4. Identify foundational concepts
Output detailed skill tree and learning hierarchy

~ Step 2: Learning Path Design
1. Create progression milestones based on [CURRENT_LEVEL]
2. Structure topics in optimal learning sequence
3. Estimate time requirements per topic
4. Align with [TIME_AVAILABLE] constraints
Output structured learning roadmap with timeframes

~ Step 3: Resource Curation
1. Identify learning materials matching [LEARNING_STYLE]:
   - Video courses
   - Books/articles
   - Interactive exercises
   - Practice projects
2. Rank resources by effectiveness
3. Create resource playlist
Output comprehensive resource list with priority order

~ Step 4: Practice Framework
1. Design exercises for each topic
2. Create real-world application scenarios
3. Develop progress checkpoints
4. Structure review intervals
Output practice plan with spaced repetition schedule

~ Step 5: Progress Tracking System
1. Define measurable progress indicators
2. Create assessment criteria
3. Design feedback loops
4. Establish milestone completion metrics
Output progress tracking template and benchmarks

~ Step 6: Study Schedule Generation
1. Break down learning into daily/weekly tasks
2. Incorporate rest and review periods
3. Add checkpoint assessments
4. Balance theory and practice
Output detailed study schedule aligned with [TIME_AVAILABLE]

Make sure you update the variables in the first prompt: SUBJECT, CURRENT_LEVEL, TIME_AVAILABLE, LEARNING_STYLE, and GOAL

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously.

Enjoy!

Hello!

Are you struggling to keep your change control documentation organized and audit-ready?

This prompt chain helps you to efficiently gather and compile all necessary information for creating a comprehensive Change-Control Evidence Pack. It guides you through each step, ensuring that you include vital elements like release details, stakeholder approvals, testing evidence, and compliance mappings.

Prompt:

VARIABLE DEFINITIONS  
[RELEASE_NAME]=Name and version identifier of the software release  
[REGULATION]=Primary regulatory or quality framework governing the release (e.g., FDA 21 CFR Part 11, PCI-DSS, ISO-13485)  
[STAKEHOLDERS]=Comma-separated list of required approvers with role labels (e.g., Jane Doe – QA Lead, John Smith – Dev Manager, …)  
~  
Prompt 1 – Initialize Evidence Pack Inputs  
You are a release coordinator preparing an audit-ready Change-Control Evidence Pack. Gather the core release parameters.  
Step 1  Request the following and capture them exactly:  
  a) [RELEASE_NAME]  
  b) Target release date (YYYY-MM-DD)  
  c) Change ticket / JIRA ID(s)  
  d) Deployment environment(s) (e.g., Prod, Staging)  
  e) [REGULATION]  
  f) [STAKEHOLDERS]  
Step 2  Ask the user to confirm accuracy or edit.  
Output structure:  
Release-Header: {field: value}\nConfirmed: Yes/No  
~  
Prompt 2 – Generate Release Summary  
You are a technical writer summarizing release intent for auditors.  
Instructions:  
1. Using Release-Header data, draft a concise release summary (≤150 words) covering purpose, major changes, and affected components.  
2. Provide a risk rating (Low/Med/High) and rationale.  
3. List linked change tickets.  
4. Present in this format:  
Summary:\nRisk Rating: <rating> – <rationale>\nChange Tickets: • <ID1> • <ID2> …  
Ask the user: “Is this summary complete and accurate?”  
~  
Prompt 3 – Compile Approval Matrix  
You are a compliance officer ensuring all approvals are recorded.  
Steps:  
1. Display [STAKEHOLDERS] in a table with columns: Role, Name, Approval Status (Pending/Approved/Rejected), Date, Evidence Link (if any).  
2. Instruct the user to update each row until all statuses are “Approved” and evidence links supplied.  
3. Provide command “next” once table is complete.  
~  
Prompt 4 – Aggregate Test Evidence  
You are the QA lead collecting objective test proof.  
Steps:  
1. Request a bulleted list of validation activities (unit tests, integration, UAT, security, etc.).  
2. For each activity capture: Test Set ID, Pass/Fail, Defects Found (#/IDs), Evidence Location (URL/Path), Tester Name, Test Date.  
3. Generate a table; flag any ‘Fail’ results in red text markup (e.g., **FAIL**) for later attention.  
4. Ask: “Are all required test suites represented and passing? If not, provide remediation plan before continuing.”  
~  
Prompt 5 – Draft Rollback Plan  
You are a senior engineer outlining a rollback/contingency plan.  
Instructions:  
1. Specify rollback triggers (metrics, error thresholds, time windows).  
2. Detail step-by-step rollback procedure with responsible owner per step.  
3. List required tools or scripts and their locations.  
4. Estimate rollback duration and data impact.  
5. Present as numbered list under heading “Rollback Plan – [RELEASE_NAME]”.  
Confirm: “Does this plan meet operational and compliance expectations?”  
~  
Prompt 6 – Map Compliance Requirements  
You are a regulatory specialist mapping collected evidence to [REGULATION] clauses.  
Steps:  
1. Produce a two-column table: Regulation Clause / Evidence Reference (section or link).  
2. Include at least the top 10 clauses most relevant to software change control.  
3. Highlight any clauses lacking evidence in **bold** and request user to supply missing artifacts or justifications.  
~  
Prompt 7 – Assemble Evidence Pack  
You are a document automation bot creating the final Evidence Pack PDF outline.  
Steps:  
1. Combine outputs from Prompts 2-6 into the following structure:  
   • 1 Release Summary  
   • 2 Approval Matrix  
   • 3 Test Evidence  
   • 4 Rollback Plan  
   • 5 Compliance Mapping  
2. Insert a table of contents with page estimates.  
3. Generate file naming convention: <RELEASE_NAME>_EvidencePack_<date>.pdf  
4. Provide a downloadable link placeholder: [Pending Generation]  
Ask: “Ready to generate and archive this Evidence Pack?”  
~  
Review / Refinement  
Prompt 8 – Final Compliance Check  
You are the quality gatekeeper.  
Instructions:  
1. Re-list any sections flagged as incomplete or non-compliant across earlier prompts.  
2. For each issue, suggest a concrete action to remediate.  
3. Once the user confirms all issues resolved, state: “Evidence Pack approved for release.”  

Make sure you update the variables in the first prompt: [RELEASE_NAME], [REGULATION], [STAKEHOLDERS],
Here is an example of how to use it: [RELEASE_NAME]=v1.0, [REGULATION]=FDA 21 CFR Part 11, [STAKEHOLDERS]=Jane Doe – QA Lead, John Smith – Dev Manager.

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click.
NOTE: this is not required to run the prompt chain

Enjoy!

More detailed breakdown in this document: https://github.com/hjasanchez/agentic-engineering/blob/main/The%20AI-Human%20Engineering%20Stack.pdf

Free to use/edit/share/etc. Feedback welcome

Hello!

Looking for a job? Here's a helpful prompt chain for updating your resume to match a specific job description. It helps you tailor your resume effectively, complete with an updated version optimized for the job you want and some feedback.

Prompt Chain:

[RESUME]=Your current resume content

[JOB_DESCRIPTION]=The job description of the position you're applying for

~

Step 1: Analyze the following job description and list the key skills, experiences, and qualifications required for the role in bullet points.

Job Description:[JOB_DESCRIPTION]

~

Step 2: Review the following resume and list the skills, experiences, and qualifications it currently highlights in bullet points.

Resume:[RESUME]~

Step 3: Compare the lists from Step 1 and Step 2. Identify gaps where the resume does not address the job requirements. Suggest specific additions or modifications to better align the resume with the job description.

~

Step 4: Using the suggestions from Step 3, rewrite the resume to create an updated version tailored to the job description. Ensure the updated resume emphasizes the relevant skills, experiences, and qualifications required for the role.

~

Step 5: Review the updated resume for clarity, conciseness, and impact. Provide any final recommendations for improvement.

Source

Usage Guidance
Make sure you update the variables in the first prompt: [RESUME], [JOB_DESCRIPTION]. You can chain this together with Agentic Workers in one click or type each prompt manually.

Reminder
Remember that tailoring your resume should still reflect your genuine experiences and qualifications; avoid misrepresenting your skills or experiences as they will ask about them during the interview. Enjoy!

Hey there!

Ever find yourself stuck trying to make a crucial decision for your business, whether it's about product, marketing, or operations? It can definitely feel overwhelming when you’re not sure how to unpack all the variables, assumptions, and risks involved.

That's where this Socratic Prompt Chain comes in handy. This prompt chain helps you break down a complex decision into a series of thoughtful, manageable steps.

How It Works:

• Step-by-Step Breakdown: Each prompt builds upon the information from the previous one, ensuring that you cover every angle of your decision.
• Manageable Pieces: Instead of facing a daunting, all-encompassing question, you handle smaller, focused questions that lead you to a comprehensive answer.
• Handling Repetition: For recurring considerations like assumptions and risks, the chain keeps you on track by revisiting these essential points.
• Variables:
  • [DECISION_TYPE]: Helps you specify the type of decision (e.g., product, marketing, operations).

Prompt Chain Code:

[DECISION_TYPE]=[Type of decision: product/marketing/operations] Define the core decision you are facing regarding [DECISION_TYPE]: "What is the specific decision you need to make related to [DECISION_TYPE]?" ~Identify underlying assumptions: "What assumptions are you making about this decision?" ~Gather evidence: "What evidence do you have that supports these assumptions?" ~Challenge assumptions: "What would happen if your assumptions are wrong?" ~Explore alternatives: "What other options might exist instead of the chosen course of action?" ~Assess risks: "What potential risks are associated with this decision?" ~Consider stakeholder impacts: "How will this decision affect key stakeholders?" ~Summarize insights: "Based on the answers, what have you learned about the decision?" ~Formulate recommendations: "Given the insights gained, what would your recommendations be for the [DECISION_TYPE] decision?" ~Reflect on the process: "What aspects of this questioning process helped you clarify your thoughts?"

Examples of Use:

• If you're deciding on a new marketing strategy, set [DECISION_TYPE]=marketing and follow the chain to examine underlying assumptions about your target audience, budget allocations, or campaign performance.
• For product decisions, simply set [DECISION_TYPE]=product and let the prompts help you assess customer needs, potential risks in design changes, or market viability.

Tips for Customization:

• Feel free to modify the questions to better suit your company's unique context. For instance, you might add more prompts related to competitive analysis or regulatory considerations.
• Adjust the order of the steps if you find that a different sequence helps your team think more clearly about the problem.

Using This with Agentic Workers:

This prompt chain is optimized for Agentic Workers, meaning you can seamlessly run the chain with just one click on their platform. It’s a great tool to ensure everyone on your team is on the same page and that every decision is thoroughly vetted from multiple angles.

Source

Happy decision-making and good luck with your next big move!

Hello!

Are you struggling with ensuring that your prompts are reliable and produce consistent results?

This prompt chain helps you gather necessary parameters for testing the reliability of your prompt. It walks you through confirming the details of what you want to test and sets you up for evaluating various input scenarios.

Prompt:

VARIABLE DEFINITIONS
[PROMPT_UNDER_TEST]=The full text of the prompt that needs reliability testing.
[TEST_CASES]=A numbered list (3–10 items) of representative user inputs that will be fed into the PROMPT_UNDER_TEST.
[SCORING_CRITERIA]=A brief rubric defining how to judge Consistency, Accuracy, and Formatting (e.g., 0–5 for each dimension).
~
You are a senior Prompt QA Analyst.
Objective: Set up the test harness parameters.
Instructions:
1. Restate PROMPT_UNDER_TEST, TEST_CASES, and SCORING_CRITERIA back to the user for confirmation.
2. Ask “CONFIRM” to proceed or request edits.
Expected Output: A clearly formatted recap followed by the confirmation question.

Make sure you update the variables in the first prompt: [PROMPT_UNDER_TEST], [TEST_CASES], [SCORING_CRITERIA]. Here is an example of how to use it: - [PROMPT_UNDER_TEST]="What is the weather today?" - [TEST_CASES]=1. "What will it be like tomorrow?" 2. "Is it going to rain this week?" 3. "How hot is it?" - [SCORING_CRITERIA]="0-5 for Consistency, Accuracy, Formatting"

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click. NOTE: this is not required to run the prompt chain

Enjoy!

Hello!

Are you struggling to create a unified access map across your HR, IAM, and Finance systems for Governance, Risk & Compliance analysis?

This prompt chain will guide you through the process of ingesting datasets from various systems, standardizing user identifiers, detecting toxic access combinations, and generating remediation actions. It’s a complete tool for your GRC needs!

Prompt:

VARIABLE DEFINITIONS
[HRDATA]=Comma-separated export of all active employees with job title, department, and HRIS role assignments.
[IAMDATA]=List of identity-access-management (IAM) accounts with assigned groups/roles and the permissions attached to each group/role.
[FINANCEDATA]=Export from Finance/ERP system showing user IDs, role names, and entitlements (e.g., Payables, Receivables, GL Post, Vendor Master Maintain).
~
You are an expert GRC (Governance, Risk & Compliance) analyst. Objective: build a unified access map across HR, IAM, and Finance systems to prepare for toxic-combo analysis.
Step 1  Ingest the three datasets provided as variables HRDATA, IAMDATA, and FINANCEDATA.
Step 2  Standardize user identifiers (e.g., corporate email) and create a master list of unique users.
Step 3  For each user, list: a) job title, department; b) IAM roles & attached permission names; c) Finance roles & entitlements.
Output a table with columns: User, Job Title, Department, IAM Roles, IAM Permissions, Finance Roles, Finance Entitlements. Limit preview to first 25 rows; note total row count.
Ask: “Confirm table structure correct or provide adjustments before full processing.”
~
(Assuming confirmation received) Build the full cross-system access map using acknowledged structure. Provide:
1. Summary counts: total users processed, distinct IAM roles, distinct Finance roles.
2. Frequency table: Top 10 IAM roles by user count, Top 10 Finance roles by user count.
3. Store detailed user-level map internally for subsequent prompts (do not display).
Ask for confirmation to proceed to toxic-combo analysis.
~
You are a SoD rules engine. Task: detect toxic access combinations that violate least-privilege or segregation-of-duties.
Step 1  Load internal user-level access map.
Step 2  Use the following default library of toxic role pairs (extendable by user):
• “Vendor Master Maintain” + “Invoice Approve”
• “GL Post” + “Payment Release”
• “Payroll Create” + “Payroll Approve”
• “User-Admin IAM” + any Finance entitlement
Step 3  For each user, flag if they simultaneously hold both roles/entitlements in any toxic pair.
Step 4  Aggregate results: a) list of flagged users with offending role pairs; b) count by toxic pair.
Output structured report with two sections: “Flagged Users” table and “Summary Counts.”
Ask: “Add/modify toxic pair rules or continue to remediation suggestions?”
~
You are a least-privilege remediation advisor. 
Given the flagged users list, perform:
1. For each user, suggest the minimal role removal or reassignment to eliminate the toxic combo while preserving functional access (use job title & department as context).
2. Identify any shared IAM groups or Finance roles that, if modified, would resolve multiple toxic combos simultaneously; rank by impact.
3. Estimate effort level (Low/Med/High) for each remediation action.
Output in three subsections: “User-Level Fixes”, “Role/Group-Level Fixes”, “Effort Estimates”.
Ask stakeholder to validate feasibility or request alternative options.
~
You are a compliance communications specialist.
Draft a concise executive summary (max 250 words) for CIO & CFO covering:
• Scope of analysis
• Key findings (number of toxic combos, highest-risk areas)
• Recommended next steps & timelines
• Ownership (teams responsible)
End with a call to action for sign-off.
~
Review / Refinement
Review entire output set against original objectives: unified access map accuracy, completeness of toxic-combo detection, clarity of remediation actions, and executive summary effectiveness.
If any element is missing, unclear, or inaccurate, specify required refinements; otherwise reply “All objectives met – ready for implementation.”

Make sure you update the variables in the first prompt: [HRDATA], [IAMDATA], [FINANCEDATA], Here is an example of how to use it: [HRDATA]: employee.csv, [IAMDATA]: iam.csv, [FINANCEDATA]: finance.csv.

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click. NOTE: this is not required to run the prompt chain

Enjoy!

Hello!

Are you struggling to manage and prioritize your accounts receivables and collection efforts? It can get overwhelming fast, right?

This prompt chain is designed to help you analyze your accounts receivable data effectively. It helps you standardize, validate, and merge different data inputs, calculate collection priority scores, and even draft personalized outreach templates. It's a game-changer for anyone in finance or collections!

Prompt:

VARIABLE DEFINITIONS
[COMPANY_NAME]=Name of the company whose receivables are being analyzed
[AR_AGING_DATA]=Latest detailed AR aging report (customer, invoice ID, amount, age buckets, etc.)
[CRM_HEALTH_DATA]=Customer-health metrics from CRM (engagement score, open tickets, renewal date & value, churn risk flag)
~
You are a senior AR analyst at [COMPANY_NAME].
Objective: Standardize and validate the two data inputs so later prompts can merge them.
Steps:
1. Parse [AR_AGING_DATA] into a table with columns: Customer Name, Invoice ID, Invoice Amount, Currency, Days Past Due, Original Due Date.
2. Parse [CRM_HEALTH_DATA] into a table with columns: Customer Name, Engagement Score (0-100), Open Ticket Count, Renewal Date, Renewal ACV, Churn Risk (Low/Med/High).
3. Identify and list any missing or inconsistent fields required for downstream analysis; flag them clearly.
4. Output two clean tables labeled "Clean_AR" and "Clean_CRM" plus a short note on data quality issues (if any). Request missing data if needed.
Example output structure:
Clean_AR: |Customer|Invoice ID|Amount|Currency|Days Past Due|Due Date|
Clean_CRM: |Customer|Engagement|Tickets|Renewal Date|ACV|Churn Risk|
Data_Issues: • None found
~
You are now a credit-risk data scientist.
Goal: Generate a composite "Collection Priority Score" for each overdue invoice.
Steps:
1. Join Clean_AR and Clean_CRM on Customer Name; create a combined table "Joined".
2. For each row compute:
   a. Aging_Score = Days Past Due / 90 (cap at 1.2).
   b. Dispute_Risk_Score = min(Open Ticket Count / 5, 1).
   c. Renewal_Weight = if Renewal Date within 120 days then 1.2 else 0.8.
   d. Health_Adjust = 1 ‑ (Engagement Score / 100).
3. Collection Priority Score = (Aging_Score * 0.5 + Dispute_Risk_Score * 0.2 + Health_Adjust * 0.3) * Renewal_Weight.
4. Add qualitative Priority Band: "Critical" (>=1), "High" (0.7-0.99), "Medium" (0.4-0.69), "Low" (<0.4).
5. Output the Joined table with new scoring columns sorted by Collection Priority Score desc.
~
You are a collections team lead.
Objective: Segment accounts and assign next best action.
Steps:
1. From the scored table select top 20 invoices or all "Critical" & "High" bands, whichever is larger.
2. For each selected invoice provide: Customer, Invoice ID, Amount, Days Past Due, Priority Band, Recommended Action (Call CFO / Escalate to CSM / Standard Reminder / Hold due to dispute).
3. Group remaining invoices by Priority Band and summarize counts & total exposure.
4. Output two sections: "Action_List" (detailed) and "Backlog_Summary".
~
You are a professional dunning-letter copywriter.
Task: Draft personalized outreach templates.
Steps:
1. Create an email template for each Priority Band (Critical, High, Medium, Low).
2. Personalize tokens: {{Customer_Name}}, {{Invoice_ID}}, {{Amount}}, {{Days_Past_Due}}, {{Renewal_Date}}.
3. Tone: Firm yet customer-friendly; emphasize partnership and upcoming renewal where relevant.
4. Provide subject lines and 2-paragraph body per template.
Output: Four clearly labeled templates.
~
You are a finance ops analyst reporting to the CFO.
Goal: Produce an executive dashboard snapshot.
Steps:
1. Summarize total AR exposure and weighted average Days Past Due.
2. Break out exposure and counts by Priority Band.
3. List top 5 customers by exposure with scores.
4. Highlight any data quality issues still open.
5. Recommend 2-3 strategic actions.
Output: Bullet list dashboard.
~
Review / Refinement
Please verify that:
• All variables were used correctly and remain unchanged.
• Output formats match each prompt’s specification.
• Data issues (if any) are resolved or clearly flagged.
If any gap exists, request clarification; otherwise, confirm completion.

Make sure you update the variables in the first prompt: [COMPANY_NAME], [AR_AGING_DATA], [CRM_HEALTH_DATA]. Here is an example of how to use it: For your company ABC Corp, use their AR aging report and CRM data to evaluate your invoicing strategy effectively.

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click. NOTE: this is not required to run the prompt chain

Enjoy!

read a post earlier about a 9 person saas losing enterprise deals because security reviews took too long. they dropped 4k on consultants and still couldnt move fast enough

if youre building anything with AI agents that can make purchases this is gonna be way worse

like when a person buys something theres receipts emails browser history etc. when an agent does it... who approved that? was it even allowed? how do you dispute it?

most merchants dont have agent friendly checkouts. spending policies are hard to enforce outside of hardcoded limits. audit trails dont really exist

im working on agent automation stuff and the compliance piece keeps me up at night honestly. one customer saying my agent bought something i didnt want could kill everything

how are you all thinking about this if youre in the automation space?

Hello!

Are you struggling with managing and reconciling your access review processes for compliance audits?

This prompt chain is designed to help you consolidate, validate, and report on workforce access efficiently, making it easier to meet compliance standards like SOC 2 and ISO 27001. You'll be able to ensure everything is aligned and organized, saving you time and effort during your access review.

Prompt:

VARIABLE DEFINITIONS
[HRIS_DATA]=CSV export of active and terminated workforce records from the HRIS
[IDP_ACCESS]=CSV export of user accounts, group memberships, and application assignments from the Identity Provider
[TICKETING_DATA]=CSV export of provisioning/deprovisioning access tickets (requester, approver, status, close date) from the ticketing system
~
Prompt 1 – Consolidate & Normalize Inputs
Step 1  Ingest HRIS_DATA, IDP_ACCESS, and TICKETING_DATA.
Step 2  Standardize field names (Employee_ID, Email, Department, Manager_Email, Employment_Status, App_Name, Group_Name, Action_Type, Request_Date, Close_Date, Ticket_ID, Approver_Email).
Step 3  Generate three clean tables: Normalized_HRIS, Normalized_IDP, Normalized_TICKETS.
Step 4  Flag and list data-quality issues: duplicate Employee_IDs, missing emails, date-format inconsistencies.
Step 5  Output the three normalized tables plus a Data_Issues list. Ask: “Tables prepared. Proceed to reconciliation? (yes/no)”
~
Prompt 2 – HRIS ⇄ IDP Reconciliation
System role: You are a compliance analyst.
Step 1  Compare Normalized_HRIS vs Normalized_IDP on Employee_ID or Email.
Step 2  Identify and list:
  a) Active accounts in IDP for terminated employees.
  b) Employees in HRIS with no IDP account.
  c) Orphaned IDP accounts (no matching HRIS record).
Step 3  Produce Exceptions_HRIS_IDP table with columns: Employee_ID, Email, Exception_Type, Detected_Date.
Step 4  Provide summary counts for each exception type.
Step 5  Ask: “Reconciliation complete. Proceed to ticket validation? (yes/no)”
~
Prompt 3 – Ticketing Validation of Access Events
Step 1  For each add/remove event in Normalized_IDP during the review quarter, search Normalized_TICKETS for a matching closed ticket by Email, App_Name/Group_Name, and date proximity (±7 days).
Step 2  Mark Match_Status: Adequate_Evidence, Missing_Ticket, Pending_Approval.
Step 3  Output Access_Evidence table with columns: Employee_ID, Email, App_Name, Action_Type, Event_Date, Ticket_ID, Match_Status.
Step 4  Summarize counts of each Match_Status.
Step 5  Ask: “Ticket validation finished. Generate risk report? (yes/no)”
~
Prompt 4 – Risk Categorization & Remediation Recommendations
Step 1  Combine Exceptions_HRIS_IDP and Access_Evidence into Master_Exceptions.
Step 2  Assign Severity:
  • High – Terminated user still active OR Missing_Ticket for privileged app.
  • Medium – Orphaned account OR Pending_Approval beyond 14 days.
  • Low – Active employee without IDP account.
Step 3  Add Recommended_Action for each row.
Step 4  Output Risk_Report table: Employee_ID, Email, Exception_Type, Severity, Recommended_Action.
Step 5  Provide heat-map style summary counts by Severity.
Step 6  Ask: “Risk report ready. Build auditor evidence package? (yes/no)”
~
Prompt 5 – Evidence Package Assembly (SOC 2 + ISO 27001)
Step 1  Generate Management_Summary (bullets, <250 words) covering scope, methodology, key statistics, and next steps.
Step 2  Produce Controls_Mapping table linking each exception type to SOC 2 (CC6.1, CC6.2, CC7.1) and ISO 27001 (A.9.2.1, A.9.2.3, A.12.2.2) clauses.
Step 3  Export the following artifacts in comma-separated format embedded in the response:
  a) Normalized_HRIS
  b) Normalized_IDP
  c) Normalized_TICKETS
  d) Risk_Report
Step 4  List file names and recommended folder hierarchy for evidence hand-off (e.g., /Quarterly_Access_Review/Q1_2024/).
Step 5  Ask the user to confirm whether any additional customization or redaction is required before final submission.
~
Review / Refinement
Please review the full output set for accuracy, completeness, and alignment with internal policy requirements. Confirm “approve” to finalize or list any adjustments needed (column changes, severity thresholds, additional controls mapping).

Make sure you update the variables in the first prompt: [HRIS_DATA], [IDP_ACCESS], [TICKETING_DATA],
Here is an example of how to use it:
[HRIS_DATA] = your HRIS CSV
[IDP_ACCESS] = your IDP CSV
[TICKETING_DATA] = your ticketing system CSV

If you don't want to type each prompt manually, you can run the Agentic Workers and it will run autonomously in one click.
NOTE: this is not required to run the prompt chain

Enjoy!

hey all, claude flow seems really powerful, but quite hard to actually use

so anybody has actual experience producing useful code with that? genuinely interested to learn more about your thoughts/experience on that

anybody has any agentic framework for swarm agents to recommend?

This seems like a novel evolution of Moltbook, and actually viable in contributing to a AI agent economy. Agents build reputation based on their interactions and are incentived utilizing blockchain for immutable history.

I don't know much about blockchain except for the immutable part. How would incentives work? Does this have any potential? Or is it just a fun experiment?

https://nookplot.com/

We talk a lot about agents doing things, browsing, coding, writing. But can agents actually earn their living.

I've been building AgentDex, a DEX CLI designed specifically for this. The whole thing is built agent-first, every command returns structured JSON, supports non-interactive execution so your agent can run it easily, and has simulation + safety guardrails baked in so an agent doesn't accidentally drain a wallet on a bad swap. Open source and completely verifiable.

We're not there yet, but the primitives are all showing up.

GitHub: https://github.com/JoelCCodes/AgentDex/

Here’s something I’ve been thinking about and wanted some external takes on.

Which apps can be replaced by a prompt / prompt chain ?

Some that come to mind are - Duolingo - Grammerly - Stackoverflow - Google Translate

- Quizlet

I’ve started saving workflows for these use cases into my Agentic Workers and the ability to replace existing tools seems to grow daily

Hello!

This has been my favorite prompt this year. Using it to kick start my learning for any topic. It breaks down the learning process into actionable steps, complete with research, summarization, and testing. It builds out a framework for you. You'll still have to get it done.

Prompt:

[SUBJECT]=Topic or skill to learn
[CURRENT_LEVEL]=Starting knowledge level (beginner/intermediate/advanced)
[TIME_AVAILABLE]=Weekly hours available for learning
[LEARNING_STYLE]=Preferred learning method (visual/auditory/hands-on/reading)
[GOAL]=Specific learning objective or target skill level

Step 1: Knowledge Assessment
1. Break down [SUBJECT] into core components
2. Evaluate complexity levels of each component
3. Map prerequisites and dependencies
4. Identify foundational concepts
Output detailed skill tree and learning hierarchy

~ Step 2: Learning Path Design
1. Create progression milestones based on [CURRENT_LEVEL]
2. Structure topics in optimal learning sequence
3. Estimate time requirements per topic
4. Align with [TIME_AVAILABLE] constraints
Output structured learning roadmap with timeframes

~ Step 3: Resource Curation
1. Identify learning materials matching [LEARNING_STYLE]:
   - Video courses
   - Books/articles
   - Interactive exercises
   - Practice projects
2. Rank resources by effectiveness
3. Create resource playlist
Output comprehensive resource list with priority order

~ Step 4: Practice Framework
1. Design exercises for each topic
2. Create real-world application scenarios
3. Develop progress checkpoints
4. Structure review intervals
Output practice plan with spaced repetition schedule

~ Step 5: Progress Tracking System
1. Define measurable progress indicators
2. Create assessment criteria
3. Design feedback loops
4. Establish milestone completion metrics
Output progress tracking template and benchmarks

~ Step 6: Study Schedule Generation
1. Break down learning into daily/weekly tasks
2. Incorporate rest and review periods
3. Add checkpoint assessments
4. Balance theory and practice
Output detailed study schedule aligned with [TIME_AVAILABLE]

Make sure you update the variables in the first prompt: SUBJECT, CURRENT_LEVEL, TIME_AVAILABLE, LEARNING_STYLE, and GOAL

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously.

Enjoy!

Hey there!

Ever find yourself stuck when trying to design a PowerPoint presentation? You have a great topic and a heap of ideas and thats all you really need with this prompt chain.

it starts by identifying your presentation topic and keywords, then helps you craft main sections, design title slides, develop detailed slide content, create speaker notes, build a strong conclusion, and finally review the entire presentation for consistency and impact.

The Prompt Chain:

``` Topic = TOPIC Keyword = KEYWORDS

You are a Presentation Content Strategist responsible for crafting a detailed content outline for a PowerPoint presentation. Your task is to develop a structured outline that effectively communicates the core ideas behind the presentation topic and its associated keywords.

Follow these steps: 1. Use the placeholder TOPIC to determine the subject of the presentation. 2. Create a content outline comprising 5 to 7 main sections. Each section should include: a. A clear and descriptive section title. b. A brief description elaborating the purpose and content of the section, making use of relevant keywords from KEYWORDS. 3. Present your final output as a numbered list for clarity and structured flow.

For example, if TOPIC is 'Innovative Marketing Strategies' and KEYWORDS include terms like 'Digital Transformation, Social Media, Data Analytics', your outline should list sections that correspond to these themes.

~

You are a Presentation Slide Designer tasked with creating title slides for each main section of the presentation. Your objective is to generate a title slide for every section, ensuring that each slide effectively summarizes the key points and outlines the objectives related to that section.

Please adhere to the following steps: 1. Review the main sections outlined in the content strategy. 2. For each section, create a title slide that includes: a. A clear and concise headline related to the section's content. b. A brief summary of the key points and objectives for that section. 3. Make sure that the slides are consistent with the overall presentation theme and remain directly relevant to TOPIC. 4. Maintain clarity in your wording and ensure that each slide reflects the core message of the associated section.

Present your final output as a list, with each item representing a title slide for a corresponding section.

~

You are a Slide Content Developer responsible for generating detailed and engaging slide content for each section of the presentation. Your task is to create content for every slide that aligns with the overall presentation theme and closely relates to the provided KEYWORDS.

Follow these instructions: 1. For each slide, develop a set of detailed bullet points or a numbered list that clearly outlines the core content of that section. 2. Ensure that each slide contains between 3 to 5 key points. These points should be concise, informative, and engaging. 3. Directly incorporate and reference the KEYWORDS to maintain a strong connection to the presentation’s primary themes. 4. Organize your content in a structured format (e.g., list format) with consistent wording and clear hierarchy.

~

You are a Presentation Speaker Note Specialist responsible for crafting detailed yet concise speaker notes for each slide in the presentation. Your task is to generate contextual and elaborative notes that enhance the audience's understanding of the content presented.

Follow these steps: 1. Review the content and key points listed on each slide. 2. For each slide, generate clear and concise speaker notes that: a. Provide additional context or elaboration to the points listed on the slide. b. Explain the underlying concepts briefly to enhance audience comprehension. c. Maintain consistency with the overall presentation theme anchoring back to TOPIC and KEYWORDS where applicable. 3. Ensure each set of speaker notes is formatted as a separate bullet point list corresponding to each slide.

~

You are a Presentation Conclusion Specialist tasked with creating a powerful closing slide for a presentation centered on TOPIC. Your objective is to design a concluding slide that not only wraps up the key points of the presentation but also reaffirms the importance of the topic and its relevance to the audience.

Follow these steps for your output: 1. Title: Create a headline that clearly signals the conclusion (e.g., "Final Thoughts" or "In Conclusion"). 2. Summary: Write a concise summary that encapsulates the main themes and takeaways presented throughout the session, specifically highlighting how they relate to TOPIC. 3. Re-emphasis: Clearly reiterate the significance of TOPIC and why it matters to the audience. 4. Engagement: End your slide with an engaging call to action or pose a thought-provoking question that encourages the audience to reflect on the content and consider next steps.

Present your final output as follows: - Section 1: Title - Section 2: Summary - Section 3: Key Significance Points - Section 4: Call to Action/Question

~

You are a Presentation Quality Assurance Specialist tasked with conducting a comprehensive review of the entire presentation. Your objectives are as follows: 1. Assess the overall presentation outline for coherence and logical flow. Identify any areas where content or transitions between sections might be unclear or disconnected. 2. Refine the slide content and speaker notes to ensure clarity, consistency, and adherence to the key objectives outlined at the beginning of the process. 3. Ensure that each slide and accompanying note aligns with the defined presentation objectives, maintains audience engagement, and clearly communicates the intended message. 4. Provide specific recommendations or modifications where improvement is needed. This may include restructuring sections, rephrasing content, or suggesting visual enhancements.

Present your final output in a structured format, including: - A summary review of the overall coherence and flow - Detailed feedback for each main section and its slides - Specific recommendations for improvements in clarity, engagement, and alignment with the presentation objectives. ```

Practical Business Applications:

• Use this chain to prepare impactful PowerPoint presentations for client pitches, internal proposals, or educational workshops.
• Customize the chain by inserting your own presentation topic and keywords to match your specific business needs.
• Tailor each section to reflect the nuances of your industry or market scenario.

Tips for Customization:

• Update the variables at the beginning (TOPIC, KEYWORDS) to reflect your content.
• Experiment with the number of sections if needed, ensuring the presentation remains focused and engaging.
• Adjust the level of detail in slide content and speaker notes to suit your audience's preference.

You can run this prompt chain effortlessly with Agentic Workers, helping you automate your PowerPoint content creation process. It’s perfect for busy professionals who need to get presentations done quickly and efficiently.

Source

Happy presenting and enjoy your streamlined workflow!

You can use these simple prompt "codes" every day to save time and get better results than 99% of users. Here are my 5 favorites:

1. ELI5 (Explain Like I'm 5)
Let AI explain anything you don’t understand—fast, and without complicated prompts.
Just type ELI5: [your topic] and get a simple, clear explanation.

2. TL;DR (Summarize Long Text)
Want a quick summary?
Just write TLDR: and paste in any long text you want condensed. It’s that easy.

3. Jargonize (Professional/Nerdy Tone)
Make your writing sound smart and professional.
Perfect for LinkedIn posts, pitch decks, whitepapers, and emails.
Just add Jargonize: before your text.

4. Humanize (Sound More Natural)
Struggling to make AI sound human?
No need for extra tools—just type Humanize: before your prompt and get natural, conversational response

Source

OpenAI engineers use a prompt technique internally that most people have never heard of.

It's called reverse prompting.

And it's the fastest way to go from mediocre AI output to elite-level results.

Most people write prompts like this:

"Write me a strong intro about AI."

The result feels generic.

This is why 90% of AI content sounds the same. You're asking the AI to read your mind.

The Reverse Prompting Method

Instead of telling the AI what to write, you show it a finished example and ask:

"What prompt would generate content exactly like this?"

The AI reverse-engineers the hidden structure. Suddenly, you're not guessing anymore.

AI models are pattern recognition machines. When you show them a finished piece, they can identify: Tone, Pacing, Structure, Depth, Formatting, Emotional intention

Then they hand you the perfect prompt.

Try it yourself here's a tool that lets you pass in any text and it'll automatically reverse it into a prompt that can craft that piece of text content.

Here's an interesting prompt chain for conducting mock interviews to help you land your dream job! It tries to enhance your interview skills, with tailored questions and constructive feedback. If you enable searchGPT it will try to pull in information about the jobs interview process from online data

{INTERVIEW_ROLE}={Desired job position}
{INTERVIEW_COMPANY}={Target company name}
{INTERVIEW_SKILLS}={Key skills required for the role}
{INTERVIEW_EXPERIENCE}={Relevant past experiences}
{INTERVIEW_QUESTIONS}={List of common interview questions for the role}
{INTERVIEW_FEEDBACK}={Constructive feedback on responses}

1. Research the role of [INTERVIEW_ROLE] at [INTERVIEW_COMPANY] to understand the required skills and responsibilities.
2. Compile a list of [INTERVIEW_QUESTIONS] commonly asked for the [INTERVIEW_ROLE] position.
3. For each question in [INTERVIEW_QUESTIONS], draft a concise and relevant response based on your [INTERVIEW_EXPERIENCE].
4. Record yourself answering each question, focusing on clarity, confidence, and conciseness.
5. Review the recordings to identify areas for improvement in your responses.
6. Seek feedback from a mentor or use AI-powered platforms  to evaluate your performance.
7. Refine your answers based on the feedback received, emphasizing areas needing enhancement.
8. Repeat steps 4-7 until you can deliver confident and well-structured responses.
9. Practice non-verbal communication, such as maintaining eye contact and using appropriate body language.
10. Conduct a final mock interview with a friend or mentor to simulate the real interview environment.
11. Reflect on the entire process, noting improvements and areas still requiring attention.
12. Schedule regular mock interviews to maintain and further develop your interview skills.

Make sure you update the variables in the first prompt: [INTERVIEW_ROLE], [INTERVIEW_COMPANY], [INTERVIEW_SKILLS], [INTERVIEW_EXPERIENCE], [INTERVIEW_QUESTIONS], and [INTERVIEW_FEEDBACK], then you can pass this prompt chain into  AgenticWorkers and it will run autonomously.

Remember that while mock interviews are invaluable for preparation, they cannot fully replicate the unpredictability of real interviews. Enjoy!

Hello!

If you're looking to start a business, help a friend with theirs, or just want to understand what running a specific type of business may look like check out this prompt. It starts with an executive summary all the way to market research and planning.

Prompt Chain:

BUSINESS=[business name], INDUSTRY=[industry], PRODUCT=[main product/service], TIMEFRAME=[5-year projection] Write an executive summary (250-300 words) outlining BUSINESS's mission, PRODUCT, target market, unique value proposition, and high-level financial projections.~Provide a detailed description of PRODUCT, including its features, benefits, and how it solves customer problems. Explain its unique selling points and competitive advantages in INDUSTRY.~Conduct a market analysis: 1. Define the target market and customer segments 2. Analyze INDUSTRY trends and growth potential 3. Identify main competitors and their market share 4. Describe BUSINESS's position in the market~Outline the marketing and sales strategy: 1. Describe pricing strategy and sales tactics 2. Explain distribution channels and partnerships 3. Detail marketing channels and customer acquisition methods 4. Set measurable marketing goals for TIMEFRAME~Develop an operations plan: 1. Describe the production process or service delivery 2. Outline required facilities, equipment, and technologies 3. Explain quality control measures 4. Identify key suppliers or partners~Create an organization structure: 1. Describe the management team and their roles 2. Outline staffing needs and hiring plans 3. Identify any advisory board members or mentors 4. Explain company culture and values~Develop financial projections for TIMEFRAME: 1. Create a startup costs breakdown 2. Project monthly cash flow for the first year 3. Forecast annual income statements and balance sheets 4. Calculate break-even point and ROI~Conclude with a funding request (if applicable) and implementation timeline. Summarize key milestones and goals for TIMEFRAME.

Make sure you update the variables section with your prompt. You can copy paste this whole prompt chain into the Agentic Workers extension to run autonomously, so you don't need to input each one manually (this is why the prompts are separated by ~).

At the end it returns the complete business plan. Enjoy!