-
Notifications
You must be signed in to change notification settings - Fork 0
docs: update skill files and add blasts skill #39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,44 @@ | ||
| --- | ||
| name: partiful-blasts | ||
| description: Send text blasts to event guests via Partiful | ||
| --- | ||
|
|
||
| # Partiful CLI — Text Blasts | ||
|
|
||
| > ⚠️ **Real SMS messages.** Blasts send actual text messages to real people's phones. Partiful prepends: *"The host of {Event} sent a Text Blast —"* before your message. | ||
|
|
||
| ## Commands | ||
|
|
||
| ### Send a Text Blast | ||
| ```bash | ||
| partiful blasts send <eventId> --message "See you tonight! Parking is on the left." --to GOING,MAYBE | ||
| partiful blasts send <eventId> --message "Updated address: 123 Main St" --to GOING --show-on-event-page | ||
| ``` | ||
|
|
||
| | Flag | Description | | ||
| |------|-------------| | ||
| | `--message <text>` | Message body (**max 480 characters**) | | ||
| | `--to <statuses>` | Comma-separated guest statuses to target (see below) | | ||
| | `--show-on-event-page` | Also display the blast on the event page | | ||
| | `--yes` | Skip the safety confirmation prompt | | ||
| | `--dry-run` | Preview recipients and message without sending | | ||
|
|
||
| ### Valid `--to` Values | ||
|
|
||
| | Status | Description | | ||
| |--------|-------------| | ||
| | `GOING` | Confirmed guests | | ||
| | `MAYBE` | Tentative guests | | ||
| | `DECLINED` | Guests who declined | | ||
| | `SENT` | Invited but no response | | ||
| | `INTERESTED` | Expressed interest | | ||
| | `WAITLIST` | On the waitlist | | ||
| | `APPROVED` | Approved from waitlist | | ||
| | `RESPONDED_TO_FIND_A_TIME` | Responded to scheduling poll | | ||
|
|
||
| ## Tips | ||
|
|
||
| - **Always use `--dry-run` first** to verify the recipient list and message. | ||
| - The 480-character limit is enforced by Partiful's API — the CLI will reject longer messages before sending. | ||
| - Without `--yes`, the CLI shows a confirmation prompt with the recipient count and message preview. | ||
| - Combine with `partiful guests list <eventId> --status going` to preview who will receive the blast. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Specify whether the 480-character limit is before or after the auto-prefixed text.
Line 20 and Line 42 mention the limit, while Line 8 states a prefix is added. Please clarify if the 480 limit applies to user-provided
--messageonly, or the final rendered SMS content including prefix.Also applies to: 42-42
🤖 Prompt for AI Agents