Prepare social post drafts from upcoming Notion calendar entries for LinkedIn, X, and Instagram. Group them with scheduled dates in Slack for human review, and mark drafted entries to prevent duplicates. It never publishes social posts.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Daily fresh-session workflow that reads the Notion content calendar for content, launches, and announcements landing within the lookahead window, drafts platform-appropriate social posts for each one, and holds the batch with the scheduled date in the Slack approval channel. Never posts to any social account.
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Query {{calendar_source}} for entries whose scheduled date falls within
{{lookahead_days}} days of today. For each entry, pull:
Kortix Drafted property.Filter out any entry where Kortix Drafted is already checked. This is the
dedup mechanism for a fresh session with no local memory — the calendar
itself is the source of truth for what's been handled.
For each remaining entry, write one draft per platform in {{platforms}},
following each platform's shape:
| Platform | Length & structure | Tone |
|---|---|---|
| 3–6 short paragraphs; can explain the "why," not just the "what"; ends with a light call to action | Explanatory, first-person-plural, low hype | |
| X | One tight post, single idea, under ~280 characters, or a short 2–4 post thread for launches with real substance | Direct, no throat-clearing, one hook |
| Short caption (2–4 sentences) plus 3–5 relevant hashtags; assumes a visual carries the rest | Casual, visual-forward |
Ground every draft in the entry's actual brief — don't invent details, stats, or claims the calendar entry doesn't support. If an entry is too thin to draft well (no brief, no description), skip it and note why in Step 5's post rather than guessing.
Label each draft with the calendar entry's title, its scheduled date, and which platform it's for, so the reviewer can scan the batch and see what's most urgent.
Post one message (or a short thread of messages) to {{approval_channel}}
containing every draft from this run, grouped by calendar entry. If an entry
was skipped for lack of context, list it separately with the reason. Post
exactly once per run — this is a fresh session, so there is nothing from a
prior run to update or merge with.
For every calendar entry you drafted for (not the skipped ones), set
Kortix Drafted to true on that entry so tomorrow's fresh run doesn't
draft it again.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Review Slack access requests against Okta role and team information, then prepare narrowly scoped GitHub or AWS IAM permissions. Apply changes only after an eligible person's approval and record the grant, reasoning, approver, and timestamp.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Research companies and people before outreach or meetings. Combines business profiles, recent news, hiring signals, and key contacts into a sourced brief with talking points and suggested questions, adding relationship history when CRM data is connected.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review daily Google Ads and Meta Ads results for budget pacing, declining performance, and unusual activity. Get prioritized findings with supporting numbers and concrete recommendations for a marketing team to assess and carry out.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Automate website tasks such as navigating pages, filling forms, clicking buttons, taking screenshots, and extracting data. The skill also supports web app testing, with specialized guides for Electron desktop apps, Slack, and cloud browsers.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Process emailed vendor invoices by extracting details, comparing them with purchase orders and invoice history, and recording duplicates, overcharges, or missing orders. Summarize results in Slack for human review; payment approval and execution remain with people.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide changes to Kortix billing code, admin controls, and pricing screens. Explain how plans, trials, enterprise contracts, and access exceptions should work, where pricing is defined, and which audited routes must handle account changes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.