sbdc-training-newsletter
Skill1 starsChanged 3 months agoMITView on GitHub
Build the Maryland SBDC monthly training newsletter end to end — parse a Neoserra training-events export into a single clean, chronological course table, merge that table into the Constant Contact newsletter template, and then generate one course-themed image at a time on request. Use whenever a consultant wants to assemble the monthly SBDC training newsletter, turn a list or PDF of upcoming training events into a formatted newsletter, aggregate Neoserra course data into a table for the newsletter, or generate images for each course in the newsletter. Covers both halves of the workflow — the data aggregation and the newsletter-plus-images production.
In this repository14 other files it gives its agents.
- business-model-canvas-helperSkill
- business-service-provider-referral-engineSkill
- client-follow-up-and-reengagementSkill
- mdsbdc-debt-helperSkill
- proposal-buddySkill
- sbdc-grant-advisorSkill
- sbdc-marketing-plan-generatorSkill
- sbdc-success-storySkill
- sbdc-underwriter-and-capital-coachSkill
- sbdc-workshopsSkill
- tam-sam-somSkill
- transcript-to-action-plan-client-emailSkill
- transcript-to-meeting-notesSkill
- transcript-to-sopSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Put the fee in the Fee column, or "No Fee" if unspecified.
- Distinctive: line 21
Use the exact source text for the Course Description column.
- Distinctive: line 22
If the user supplies an external list or correction that overrides the export (e.g., $20 vs.
- Distinctive: line 33
Keep the template's headings, bullet points, "Register Here" placeholders, and formatting intact.
- Distinctive: line 34
Verify every course's date, time, instructor, fee, and description matches the table exactly — this is the step where transcription errors …
- Distinctive: line 43
Write a short text-to-image prompt describing a scene or concept that visually represents that course's topic — name the style, key …
- Distinctive: line 46
Only generate one course image per "Next" so the consultant can review and request changes before moving on.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SBDC Training Newsletter
This skill builds the Maryland SBDC monthly training newsletter in three stages: aggregate the raw training-event data into one clean table, render that table into the newsletter, and generate a themed image per course on demand. The two halves used to be separate tools; they are one pipeline — the table the aggregation step produces is exactly what the newsletter step consumes. Data integrity is the throughline: every date, time, fee, and instructor has to survive from the Neoserra export to the finished newsletter unchanged.
Stage 1 — Aggregate the events into one table
Input is a Neoserra training-events export (PDF or text) for the target month, plus any user-provided corrections or updates. Parse every event and produce a single, chronological table with these columns:
| Date | Time | Event Title | Fee | Format | Topic | Location | Instructor | Course Description (from source) |
Rules:
- Normalize date and time to a consistent, human-readable format (e.g., "March 5, 2026", "1:00PM – 2:00PM").
- Put the fee in the Fee column, or "No Fee" if unspecified.
- Reflect online / in-person / hybrid status in the Format column.
- Use the exact source text for the Course Description column.
- If the user supplies an external list or correction that overrides the export (e.g., $20 vs. $25), incorporate it, resolving discrepancies to the best-known value.
- For any missing field, write "(Not listed)" or "(No data)" rather than leaving it blank — never drop the rest of a row over one missing field.
- Sort ascending by date, then time. Ensure no event is duplicated.
Output the aggregated table on its own first, so the consultant can confirm the data before it goes into the newsletter.
Stage 2 — Merge the table into the newsletter
Take the confirmed course table and the newsletter template (the consultant provides the Constant Contact template, or asks you to use the standard monthly layout) and produce the final, consolidated newsletter:
- Fill each course section of the template from the table.
- Keep the template's headings, bullet points, "Register Here" placeholders, and formatting intact.
- Verify every course's date, time, instructor, fee, and description matches the table exactly — this is the step where transcription errors creep in, so double-check.
Present the complete newsletter as a single, final piece of text.
Stage 3 — Generate course images one at a time
Image generation is part of the deliverable, not an afterthought. After the newsletter is assembled, wait for the consultant to say "Next", and then generate an image for one course at a time, in newsletter order:
- Identify which course is next in sequence.
- Write a short text-to-image prompt describing a scene or concept that visually represents that course's topic — name the style, key objects, and background.
- Produce the image (or the image prompt, if the surface has no image model), then confirm and offer to proceed to the next course.
Only generate one course image per "Next" so the consultant can review and request changes before moving on. Keep the visual style consistent across the set so the newsletter reads as one piece.
Throughout
Keep responses clear and user-friendly. The two failure modes to guard against are data drift (a fee or instructor that changed between the export and the newsletter) and formatting drift (a course section that doesn't match the template) — check for both before calling the newsletter done.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

