drive-get-permissions
Google Drive のファイルの共有設定を確認する。「共有状況確認」「誰がアクセスできる」「共有設定を見せて」「アクセス権確認」「権限一覧」「共有中のユーザー」などで起動。
Best use case
drive-get-permissions is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Google Drive のファイルの共有設定を確認する。「共有状況確認」「誰がアクセスできる」「共有設定を見せて」「アクセス権確認」「権限一覧」「共有中のユーザー」などで起動。
Teams using drive-get-permissions should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/drive-get-permissions/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How drive-get-permissions Compares
| Feature / Agent | drive-get-permissions | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Google Drive のファイルの共有設定を確認する。「共有状況確認」「誰がアクセスできる」「共有設定を見せて」「アクセス権確認」「権限一覧」「共有中のユーザー」などで起動。
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Drive Get Permissions Google Drive のファイルの共有設定を確認します。 ## 引数 - ファイルID (必須): 共有設定を確認するファイルのID ## 実行方法 ```bash python plugins/shiiman-google/skills/drive-list/scripts/google_drive.py permissions --file-id <file-id> ``` ## 使用例 ```bash python plugins/shiiman-google/skills/drive-list/scripts/google_drive.py permissions --file-id 1abc...xyz ``` ## 出力項目 - role: 権限レベル（owner, writer, reader など） - type: 共有タイプ（user, group, domain, anyone） - emailAddress: 共有相手のメールアドレス
Related Skills
spec-driven-development
Guide for implementing Specification-Driven Development in any project using GitHub's spec-kit. Use when users want to start spec-driven development, need to initialize spec-kit in a project, or want guidance on the spec-kit workflow (constitution, specify, clarify, plan, tasks, implement). Covers installation, initialization, and step-by-step prompts for each phase.
pipedrive-automation
Automate Pipedrive CRM operations including deals, contacts, organizations, activities, notes, and pipeline management via Rube MCP (Composio). Always search tools first for current schemas.
googledrive-automation
Automate Google Drive tasks via Rube MCP (Composio). Always search tools first for current schemas.
acceptance-test-driven-development
Write acceptance tests before unit tests to ensure you're building the right thing
spec_driven_development.constitution
Creates foundational governance principles and development guidelines for the project. Use when starting a new project or establishing standards.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
proof-driven-development
Run proof-driven development using Lean 4 for formal verification - comprehensive skill handling both design (planning) and execution (verification)
context-driven-development
Use this skill when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md, and...
spec-driven-dev
基于 OpenSpec 规范的开发专家。负责全生命周期管理：初始化项目、创建变更提案 (Proposal)、制定规范 (Specs)、技术设计 (Design) 及任务规划 (Tasks)。严格遵守 OpenSpec 目录结构与工作流。
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
event-driven
Event-driven architecture patterns including message queues, pub/sub, event sourcing, CQRS, and sagas. Use when implementing async messaging, distributed transactions, event stores, command query separation, domain events, integration events, data streaming, choreography, orchestration, or integrating with RabbitMQ, Kafka, Apache Pulsar, AWS SQS, AWS SNS, NATS, event buses, or message brokers.
domain-driven-design
Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns.