Composio Cloud Tools
quarqlabs/argus
Routes requests to external SaaS apps such as GitHub, Gmail, Google Calendar, Slack, Notion and Linear through cloud tools, with safeguards on irreversible actions.
Schedule meetings, calls, or events on the calendar. An agent skill from juliepy/AI-Engineer-from-scrach.
Install Schedule Meeting
$ npx skills add juliepy/AI-Engineer-from-scrach --skill schedule-meeting -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install juliepy/AI-Engineer-from-scrach schedule-meeting --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/juliepy/AI-Engineer-from-scrach.git skills-src && mkdir -p .claude/skills && cp -r skills-src/12-hermes-agent-small/skills/schedule-meeting .claude/skills/schedule-meeting && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "schedule-meeting" agent skill from https://github.com/juliepy/AI-Engineer-from-scrach/tree/main/12-hermes-agent-small/skills/schedule-meeting into .claude/skills/schedule-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schedule-meeting", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/juliepy/AI-Engineer-from-scrach/tree/main/12-hermes-agent-small/skills/schedule-meetingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add juliepy/AI-Engineer-from-scrach --skill schedule-meeting -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install juliepy/AI-Engineer-from-scrach schedule-meeting --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/juliepy/AI-Engineer-from-scrach.git skills-src && mkdir -p .agents/skills && cp -r skills-src/12-hermes-agent-small/skills/schedule-meeting .agents/skills/schedule-meeting && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "schedule-meeting" agent skill from https://github.com/juliepy/AI-Engineer-from-scrach/tree/main/12-hermes-agent-small/skills/schedule-meeting into .agents/skills/schedule-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schedule-meeting", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add juliepy/AI-Engineer-from-scrach --skill schedule-meeting -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install juliepy/AI-Engineer-from-scrach schedule-meeting --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/juliepy/AI-Engineer-from-scrach.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/12-hermes-agent-small/skills/schedule-meeting .cursor/skills/schedule-meeting && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "schedule-meeting" agent skill from https://github.com/juliepy/AI-Engineer-from-scrach/tree/main/12-hermes-agent-small/skills/schedule-meeting into .cursor/skills/schedule-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schedule-meeting", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/juliepy/AI-Engineer-from-scrach.git --path 12-hermes-agent-small/skills/schedule-meeting--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add juliepy/AI-Engineer-from-scrach --skill schedule-meeting -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install juliepy/AI-Engineer-from-scrach schedule-meeting --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/juliepy/AI-Engineer-from-scrach.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/12-hermes-agent-small/skills/schedule-meeting .gemini/skills/schedule-meeting && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "schedule-meeting" agent skill from https://github.com/juliepy/AI-Engineer-from-scrach/tree/main/12-hermes-agent-small/skills/schedule-meeting into .gemini/skills/schedule-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schedule-meeting", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install juliepy/AI-Engineer-from-scrach schedule-meetingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add juliepy/AI-Engineer-from-scrach --skill schedule-meeting -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/juliepy/AI-Engineer-from-scrach.git skills-src && mkdir -p .github/skills && cp -r skills-src/12-hermes-agent-small/skills/schedule-meeting .github/skills/schedule-meeting && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "schedule-meeting" agent skill from https://github.com/juliepy/AI-Engineer-from-scrach/tree/main/12-hermes-agent-small/skills/schedule-meeting into .github/skills/schedule-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schedule-meeting", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add juliepy/AI-Engineer-from-scrach --skill schedule-meeting -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install juliepy/AI-Engineer-from-scrach schedule-meeting --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/juliepy/AI-Engineer-from-scrach.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/12-hermes-agent-small/skills/schedule-meeting .opencode/skills/schedule-meeting && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "schedule-meeting" agent skill from https://github.com/juliepy/AI-Engineer-from-scrach/tree/main/12-hermes-agent-small/skills/schedule-meeting into .opencode/skills/schedule-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schedule-meeting", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
schedule-meeting- GitHub stars
- 441
- Token cost
- ~317 tokens
- SKILL.md length
- 158 words
- Files
- 1
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- None found
At a glance
Schedule meetings, calls, or events on the calendar. An agent skill from juliepy/AI-Engineer-from-scrach.
- Works in 5 steps: Resolve relative dates ("next Tuesday",… → Check memory context for the attendee's… → Call create_event with a short, specific… → …
- The user wants to book
- SKILL.md covers How to schedule well and Edge cases
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Schedule Meeting is an agent skill from juliepy/AI-Engineer-from-scrach. Schedule meetings, calls, or events on the calendar. Use when the user wants to book, plan, schedule, or set up a meeting or appointment with someone at a time.
Its SKILL.md is about 320 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Productivity & Automation, covering Calendar and scheduling.
When your agent uses it
- The user wants to book
- Set up a meeting
- Appointment with someone at a time
Example prompts
- “/schedule-meeting”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Resolve relative dates ("next Tuesday", "tomorrow morning") into ISO 8601
- Check memory context for the attendee's preferences (e.g. "prefers morning
- Call create_event with a short, specific title: "Coffee with Alex", not
- If the user mentioned an agenda or context, put it in notes.
- After creating, confirm in one sentence: what, when, with whom.
What it can do on your machine
Read from SKILL.md and the folder at commit d9e02cb. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Schedule Meeting loads about 317 tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 158 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 158 words (~317 tokens).
“using today's date from the system prompt. Morning = 09:00, afternoon = 14:00, evening = 18:00 unless the user says otherwise.”
- name
- schedule-meeting
Files
Just SKILL.md in 12-hermes-agent-small/skills/schedule-meeting of juliepy/AI-Engineer-from-scrach.
Open the folder on GitHubat commit d9e02cb
Compare with similar skills
Schedule Meeting next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Schedule Meeting this skilljuliepy/AI-Engineer-from-scrach | 441 | — | ~317 | Automated safety check: Pass | None | |
| Composio Cloud Toolsquarqlabs/argus | 279 | — | ~543 | Automated safety check: Pass | Apache-2.0 | |
| Executive AssistantTheCraigHewitt/hermes-chief-of-staff | 104 | — | ~1k | Automated safety check: Pass | MIT | |
| Atlassian Jira Syncitseffi/agentic-os | 114 | — | ~515 | Automated safety check: Pass | MIT | |
| Todays Daily Plantwhsi/skills | 259 | — | ~1.2k | Automated safety check: Pass | None | |
| Google Calendar Schedule Checkitseffi/agentic-os | 114 | — | ~467 | Automated safety check: Pass | MIT |
Similar skills
Executive Assistant
TheCraigHewitt/hermes-chief-of-staff
Triage inbox, draft emails, manage calendar, schedule meetings, handle routine communications.
Atlassian Jira Sync
itseffi/agentic-os
Sync Jira issues with local tasks. An agent skill from itseffi/agentic-os.
Todays Daily Plan
twhsi/skills
Write spoken daily planning notes into an Obsidian Mandala Grid day-plan Markdown file.
Google Calendar Schedule Check
itseffi/agentic-os
Check Google Calendar for today's schedule. An agent skill from itseffi/agentic-os.
Granola Meeting Sync
itseffi/agentic-os
Sync new Granola meetings to local Knowledge folder. An agent skill from itseffi/agentic-os.
More from juliepy/AI-Engineer-from-scrach
All 15 skills in this repoHarness Creator
juliepy/AI-Engineer-from-scrach
Build, audit, and improve lightweight harnesses for AI coding agents: AGENTS.md/CLAUDE.md, feature state, verification workflows, scope boundaries, lifecycle handoff, memory persistence, context…
PR Worktree
juliepy/AI-Engineer-from-scrach
Create and tear down the throwaway git worktrees used to test community PRs for waku-agent, without leaking API keys or leaving branches behind.
Review PR
juliepy/AI-Engineer-from-scrach
Review an incoming community PR for waku-agent and present it Sean's way — bilingual (English + 中文), three fixed sections: what they did & why it matters, verdict (merge / change / close), and how…
Implement
juliepy/AI-Engineer-from-scrach
Read a plan file, execute every task in dependency order with per-task validation, then write an implementation report to reports/<feature-slug-implementation-report.md.
Plan
juliepy/AI-Engineer-from-scrach
Analyze a ticket or feature description, read the codebase, identify risks, and write a context-rich implementation plan to plans/<feature-slug-plan.md.
Validate
juliepy/AI-Engineer-from-scrach
Run the full quality gate (ruff + mypy + pytest + tsc + vitest) and report PASS/FAIL for each command.
Related
Categories
Questions about Schedule Meeting
What does Schedule Meeting do?
Schedule meetings, calls, or events on the calendar. An agent skill from juliepy/AI-Engineer-from-scrach. Schedule Meeting is an agent skill from juliepy/AI-Engineer-from-scrach. Schedule meetings, calls, or events on the calendar.
When should I use Schedule Meeting?
Schedule Meeting fits situations like: the user wants to book; set up a meeting; appointment with someone at a time.
How do I install Schedule Meeting in Claude Code?
Run `npx skills add juliepy/AI-Engineer-from-scrach --skill schedule-meeting -a claude-code`. Or copy the skill folder (12-hermes-agent-small/skills/schedule-meeting in juliepy/AI-Engineer-from-scrach) into .claude/skills/schedule-meeting in your project. Claude Code loads it when a task matches its description.
How do I install Schedule Meeting in Codex?
Run `npx skills add juliepy/AI-Engineer-from-scrach --skill schedule-meeting -a codex`. Or copy the skill folder (12-hermes-agent-small/skills/schedule-meeting in juliepy/AI-Engineer-from-scrach) into .agents/skills/schedule-meeting in your project. Codex loads it when a task matches its description.
Can I use Schedule Meeting in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add juliepy/AI-Engineer-from-scrach --skill schedule-meeting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/schedule-meeting, .gemini/skills/schedule-meeting, .github/skills/schedule-meeting and .opencode/skills/schedule-meeting in your project.
What does Schedule Meeting need to run?
SKILL.md names no scripts, command-line tools or credentials: Schedule Meeting is instructions for the agent only.
Does Schedule Meeting access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Schedule Meeting safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Schedule Meeting use?
No licence was found for Schedule Meeting or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Schedule Meeting use?
About 317 tokens (SKILL.md is roughly 1.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Schedule Meeting?
Skills that share tags, products or a category with Schedule Meeting: Composio Cloud Tools (quarqlabs/argus, 279 stars), Executive Assistant (TheCraigHewitt/hermes-chief-of-staff, 104 stars), Atlassian Jira Sync (itseffi/agentic-os, 114 stars) and Todays Daily Plan (twhsi/skills, 259 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Schedule Meeting?
juliepy (a GitHub user) maintains it in juliepy/AI-Engineer-from-scrach, which has 441 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on September 6, 2026.
Source: juliepy/AI-Engineer-from-scrach on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.