kjannette/deClawed
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

.

Browse Source
This commit is contained in:
KS Jannette
2026-08-14 15:00:10 -04:00
parent cfcac8607c
commit c22d616595
1 changed files with 12 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
src/prompts/classify-emails.txt
View File

@@ -29,7 +29,9 @@ Category D - Other
The email does not fit into categories A, B, or C. This includes non-job-application emails, newsletters, promotional content, or ambiguous messages that do not clearly match another category.
STEP 3: STAR REVIEWED EMAILS
- For EVERY single email you reviewed in this run (Categories A, B, C, and D), apply the Gmail "STARRED" system label or use your email tool to add a star to the message.
For every Category A, C, and D email, apply the Gmail "STARRED" system label or use your email tool to add a star to the message.
DO NOT add a star to any Category B email.
STEP 4: Confirm, via the chat window, the total number of emails fetched.
@@ -42,12 +44,15 @@ For each, state:
5. Summary of body
STEP 6: Process check **STRICT COMPLIANCE REQUIRED** **DO NOT FORGET***:
Summarize all "Category B" and "Category D" emails in the chat.
Star all reviewed email
Next, perform the following actions for each "Category B" email:
Summarize all "Category B" and "Category D" emails in the chat.
Star all emails reviewed and classified as Category A, C or D.
Do not star emails reviewed and classified as Category B.
Do not star unreviewed emails.
STEP 7: CREATE CALENDAR EVENTS
Perform the following actions for each "Category B" email:
Immediately after logging to the spreadsheet, check whether ANY of these fields were populated or updated:
- Recruiter Call Scheduled
- Company First Interview
@@ -61,9 +66,7 @@ For EACH of the above fields that contains a date/time, create a Google Calendar
- Description: include recruiter or company contact name/email/phone, and note whether they have your cell number
STRICT CONSTRAINTS:
- Do not make up phone numbers, links, dates, or anything at all. If it does not exist in text within a verifiable email, IT DOES NOT EXIST.
- PAST-DATE CHECK: Before creating a calendar event: 1) verify today's date from an external, reliable source; 2) compare the proposed meeting date/time against today's date; 3) if the meeting date has already passed, do NOT create a calendar event for it.
- Each new date/time value in a scheduling column = one new calendar event.
- Do not make up phone numbers, links, dates, or anything at all. If information does not exist in text within a verifiable email message, IT DOES NOT EXIST.
- Before creating a calendar event: 1) verify today's date from an external, reliable source; 2) compare the proposed meeting date/time against today's date; 3) if the meeting date has already passed, do NOT create a calendar event for it.
- Always use the same account for calendar events as was used for email fetching.
- Do not create duplicate calendar events for the same meeting (same company representative && same job description | same company && same date time)
- If information is not present in an email, leave that field empty - do not guess or make up information.