007
無料Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.
日本語の概要は準備中です。原文の説明を表示しています。
Add Google Calendar integration to Deus. Agents can list, create, update, and delete calendar events. Guides through GCP OAuth setup, token generation, keep-alive timer, and CLI command installation.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
This skill adds Google Calendar tools to Deus container agents via the built-in @deus-ai/gcal-mcp package. Once set up, agents can list events, create meetings, check availability, and manage calendars from any channel.
ls integrations/gcal/credentials.json 2>/dev/null && echo "CREDS_EXIST" || echo "NO_CREDS"
ls integrations/gcal/tokens.json 2>/dev/null && echo "TOKENS_EXIST" || echo "NO_TOKENS"
ls packages/mcp-gcal/dist/index.js 2>/dev/null && echo "PACKAGE_BUILT" || echo "NOT_BUILT"
Tell the user:
I need you to create Google Cloud OAuth credentials. This is a one-time setup:
- Open https://console.cloud.google.com - create a new project or select an existing one
- Go to APIs & Services > Library, search "Google Calendar API", click Enable
- Go to APIs & Services > Credentials, click + CREATE CREDENTIALS > OAuth client ID
- If prompted for a consent screen: choose External, fill in app name ("Deus") and your email, save
- Application type: Desktop app, name: "Deus"
- Click DOWNLOAD JSON and tell me where you saved it (or paste the contents)
Once the user provides the file path or JSON content:
mkdir -p integrations/gcal
If user gave a path:
cp "<user-provided-path>" integrations/gcal/credentials.json
If user pasted JSON, write it to integrations/gcal/credentials.json.
Verify the file is gitignored:
git check-ignore integrations/gcal/credentials.json || echo "WARNING: credentials.json is NOT gitignored"
cd packages/mcp-gcal && npm install && npm run build && cd ../..
npm list googleapis 2>/dev/null | grep -q googleapis || npm install --no-save googleapis
Tell the user:
I'll start the Google Calendar authorization. A URL will appear - open it in your browser, sign in with your Google account, and grant calendar access. Then paste the authorization code back here.
node scripts/setup-gcal-auth.mjs
This is interactive - the user must paste the code. The script saves tokens to integrations/gcal/tokens.json and verifies the connection.
If the script can't run interactively (e.g., in a container), tell the user:
Run this in a separate terminal:
node scripts/setup-gcal-auth.mjsLet me know when it's done.
ls -la integrations/gcal/tokens.json
deus gcal ping
Expected output: gcal ping OK: <user-email>
If deus gcal command is not found, the CLI may not have the latest version. Run:
deus auth
The container agent-runner auto-detects gcal when all three files exist:
packages/mcp-gcal/dist/index.jsintegrations/gcal/credentials.jsonintegrations/gcal/tokens.jsonNo manual container configuration is needed.
The Google OAuth refresh token expires after ~7 days of inactivity. Install a daily keep-alive to prevent this:
cp setup/com.deus.gcal-keepalive.plist ~/Library/LaunchAgents/
launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/com.deus.gcal-keepalive.plist 2>/dev/null || launchctl kickstart gui/$(id -u)/com.deus.gcal-keepalive
Verify it's running:
launchctl list | grep gcal-keepalive
Create a systemd timer instead:
mkdir -p ~/.config/systemd/user
cat > ~/.config/systemd/user/deus-gcal-keepalive.service << 'EOF'
[Unit]
Description=Deus Google Calendar keep-alive
[Service]
Type=oneshot
ExecStart=/usr/local/bin/deus gcal ping
EOF
cat > ~/.config/systemd/user/deus-gcal-keepalive.timer << 'EOF'
[Unit]
Description=Daily Deus gcal keep-alive
[Timer]
OnCalendar=daily
Persistent=true
[Install]
WantedBy=timers.target
EOF
systemctl --user enable --now deus-gcal-keepalive.timer
deus auth
Tell the user:
Google Calendar is now connected. Your agents can list events, create meetings, and check availability from any channel.
CLI commands:
deus gcal- show token statusdeus gcal auth- re-authorize (if token expires)deus gcal ping- test connection / keep token aliveFrom chat: Just ask naturally - "What's on my calendar tomorrow?", "Schedule a meeting at 3pm", etc.
Remove the keep-alive timer:
launchctl bootout gui/$(id -u)/com.deus.gcal-keepalive 2>/dev/null
rm ~/Library/LaunchAgents/com.deus.gcal-keepalive.plist
Remove tokens (keeps credentials for easy re-setup):
rm integrations/gcal/tokens.json
Remove everything:
rm -rf integrations/gcal/
Restart Deus:
deus auth
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.
日本語の概要は準備中です。原文の説明を表示しています。
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
日本語の概要は準備中です。原文の説明を表示しています。
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR. Part of cursor-rules-java project
日本語の概要は準備中です。原文の説明を表示しています。
Run a health check on an existing project: dependency audit, security scan, test runner detection, CI/CD evaluation, and missing configuration analysis. Maps the three execution gates (pre/in/post) from /10x-bootstrapper to an assessment framework for existing codebases. Reads optional context/foundation/stack-assessment.md from /10x-stack-assess to focus checks on identified gaps. Writes context/foundation/health-check.md with findings, prioritized fixes, and an agent-readiness verdict. Use when the user has an existing project and wants to verify its health before working with an agent. Trigger phrases: "health check", "check my project", "audit my project", "is my project healthy", "sprawdź projekt", "audyt projektu", "health-check", "project health". Use AFTER /10x-stack-assess (brownfield chain), BEFORE agent onboarding (m1-l4).
日本語の概要は準備中です。原文の説明を表示しています。
You MUST use this when building projects end-to-end. Orchestrates all 12 team roles — automatically switches between CTO, architect, PM, engineers, SRE, security, DBA, QA, and EM based on the current phase of work. Starts with brainstorming before any implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) — through a consultative, modular step-by-step approach that only adds what you actually need. This should trigger for requests such as Add Maven plugins in pom.xml; Improve Maven plugins in pom.xml. Part of cursor-rules-java project
日本語の概要は準備中です。原文の説明を表示しています。