Conference Shared Calendar

Organization

swan-gtm

conference-shared-calendar

Create or maintain a shared conference reference calendar from an official agenda, including sessions, side events, sharing permissions, timezone checks, and duplicate-safe updates. Use when a participant or team wants a shared event calendar or an importable agenda.

Overview

Publisher	swan-gtm
Repository	`gtm-skills`
Skill name	`conference-shared-calendar`
Stars	216
Forks	103
Bundled files	3
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
3 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by swan-gtm on GitHub. Read the source before you install it.

Installation

Install the Conference Shared Calendar AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/swan-gtm/gtm-skills/tree/main/skills/ariel-cohen/conference-shared-calendar
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/swan-gtm/gtm-skills/tree/main/skills/ariel-cohen/conference-shared-calendar

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/swan-gtm/gtm-skills.git /tmp/gtm-skills
mkdir -p .claude/skills
cp -r /tmp/gtm-skills/skills/ariel-cohen/conference-shared-calendar .claude/skills/conference-shared-calendar

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Conference Shared Calendar in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Conference Shared Calendar on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Conference Shared Calendar is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Shared conference calendar

Create a useful reference agenda that does not consume people's meeting availability.

Establish the inputs

Use assets/calendar-worksheet.md. Reuse information already supplied. Ask only for missing facts that affect correctness: official source, event dates, venue IANA timezone, calendar owner/destination, and intended readers/editors. Never infer timezone from the operator's computer. Distinguish a private team calendar from a publicly shared event calendar.

Inspect the existing destination and prior imports before creating anything. Prefer an authorized existing calendar when it serves the purpose. Use a connector/API when available; otherwise use the authenticated browser. With no live access, prepare an ICS and exact setup instructions and label the live setup unfinished.

Normalize the agenda

Read the official agenda and linked session details. Capture source ID, title, date, start/end, timezone, venue/room, speaker, source URL, and confidence. Retain concurrent sessions; this is a reference calendar, not one person's itinerary. Do not copy private notes into shared descriptions.

Prefer explicit organizer updates over stale listings. Keep a source/change log and flag contradictions. Never turn an unpublished time into a precise appointment: a known date may have a Free all-day “TIME TBD” marker; unknown dates stay in a separate unresolved list. Do not confuse a short public workshop with an independently arranged longer activity.

Build and publish

Create a separately named reference calendar with the venue timezone. Verify the destination before importing or writing.
Make reference events Free / transparent. Colors are cosmetic. Sharing “see only free/busy” is a visibility permission and is different from event Free/Busy status.
Include source links and useful logistics. A reference copy of a dinner does not accept the original invitation or add guests. Do not add ATTENDEE fields to an ICS reference export.
Prefer API upserts with a saved source-ID → remote-event-ID mapping for ongoing maintenance. If using ICS, assign stable UIDs from conference namespace plus source ID; use valid timezone-aware times, CRLF, escaped text, UTF-8-safe 75-octet line folding, and exclusive all-day end dates. Validate event counts, ordering, and sample times before import.
ICS import is a snapshot. Stable UIDs alone do not guarantee that repeated Google imports update existing entries. Do not reimport blindly. Inspect and update the existing records, or prepare a deliberate replacement plan without deleting unrelated events.
Apply the requested sharing permissions. Give viewers event details and editors only the intended editing rights. Public access is a separate explicit choice. If sharing would notify people and the user has not authorized invitations, finish the calendar and present the exact recipients/permissions for approval.

Read references/google-calendar.md for provider steps and sources.

Verify and hand off

Compare imported event count against the normalized agenda, accounting for pre-existing records. Check first/last dates, simultaneous sessions, room names, one all-day marker, and timezone rendering. Confirm events are Free and sharing matches the requested scope. Check recipient visibility when access permits; otherwise report it unverified.

Return the calendar link or ICS path, source timestamp, counts, permissions, unresolved times, and update instructions. Save the ID mapping/change log privately with the user's project, not inside the distributable skill. Recommend placing selected sessions and duties on each attendee's own calendar as Busy; use conference-personal-plan if installed.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Conference Shared Calendar AI skill do?

Why use Conference Shared Calendar on TypingMind?

Because you install it once and use it with any model. Conference Shared Calendar is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Conference Shared Calendar in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/swan-gtm/gtm-skills/tree/main/skills/ariel-cohen/conference-shared-calendar. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Conference Shared Calendar?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Conference Shared Calendar?

As many as you like. As long as a model supports skills, you can use Conference Shared Calendar with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Conference Shared Calendar AI skill free?

Yes. It is published on GitHub by swan-gtm under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Gh Stack

vercel

OrganizationPopular

Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or…

Agent Transcript

Requested GitHub PR/issue agent transcripts: redact, trim, preview, and insert safely.

Openclaw Refactor Docs

openclaw

OrganizationPopular

Refactor an existing OpenClaw docs page with source-audited preservation, restructuring, and verification.

Gemini

Gemini CLI one-shot prompts, summaries, generation, skills, hooks, MCP, or Gemma routing.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Shared conference calendar

Establish the inputs

Normalize the agenda

Build and publish

Verify and hand off

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now