forked from elizaOS/eliza
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #24 from blockydevs/feat/linkedin-client-posts-gen…
…erating-improvements fix: client posts generating improvements
- Loading branch information
Showing
10 changed files
with
118 additions
and
25 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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 |
---|---|---|
@@ -1 +1 @@ | ||
{"version": "0.1.8+build.1"} | ||
{"version": "0.1.9-alpha.1"} |
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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,34 @@ | ||
export const createLinkedinPostTemplate = ` | ||
You are an AI assistant specialized in creating LinkedIn content. Given the {{state}} and LINKEDIN_POST {{topics}}, create a captivating and relevant LinkedIn post. | ||
Content Structure: | ||
1. Start with a specific fact or insight about the selected (randomly) topic from {{topics}} or somehow connected to one of them. | ||
2. Explain why this concept is important for the target audience. | ||
3. Provide a clear technical example related to the topic. | ||
4. Share one specific implementation detail. | ||
5. End with a technical discussion question. | ||
6. Add 3-4 relevant technical hashtags at the end. | ||
Style Guidelines: | ||
- Maintain high technical accuracy. | ||
- Use terminology appropriate for intermediate professionals. | ||
- Keep a professional tone, focusing on knowledge sharing, not opinions. | ||
- Length: 800-1200 characters. | ||
- Avoid personal stories, career advice, or company-specific details. | ||
- Don't use first-person narrative. | ||
Formatting: | ||
- Use normal text for rest of post | ||
- Use emojis sparingly. | ||
Hashtags: | ||
- Include 3-4 relevant technical hashtags related to the topic (without spaces). | ||
Avoid: | ||
- Generic advice, motivational content, personal experiences, company-specific information, markdown formatting. | ||
- Post similar to published post from {{state}}, first try to create post about topic not mentioned in {{state}}, if all topics are mentioned in {{state}} then create post about topic that is not mentioned in {{state}} but is related to one of the topics from {{state}}. | ||
- Markdown formatting. | ||
Important Note: | ||
- Ensure that the reply strictly adheres to the formatting rules provided in the prompt, especially avoiding markdown formatting and using the specified text styles for bold, italics, and bold italics. | ||
`; |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.