Automated summary
Checks the sharing settings of a Google Drive file and lists its access permissions (role, sharing type, email address) from the file ID.
Strengths
- Returns role (owner, writer, reader…), type (user, group, domain, anyone) and email address for each permission entry
- Read-only operation: no sharing is created, changed or revoked
- Triggers on common Japanese phrasing such as "who can access this" or "show the sharing settings"
Limitations
- Requires the file ID; lookup by file name or URL is not supported
- Depends on the shiiman-google plugin's Python script and pre-configured Google credentials
- Inspection only: it cannot fix or revoke any access
Use it when you need to quickly audit who can access a specific Drive file and at what level.
Avoid it if you need to change or revoke sharing, or if you only have a file name without its ID.
Security analysis
CautionThe skill is a legitimate Google Drive permissions checker, but it invokes a local Python script via Bash and accesses potentially sensitive sharing data. There are no destructive, exfiltration, or obfuscated instructions, so it is not risky, but it warrants caution due to Bash execution and external API access.
- •Uses Bash to execute a local Python script whose contents are not shown, so trust depends on the installed plugin script.
- •Accesses Google Drive sharing metadata and may output email addresses, which can be sensitive.
- •The file ID argument is interpolated into a shell command; agents should avoid unsafe shell expansion for untrusted values.
Examples
このファイルの共有状況を確認して。ファイルIDは 1abc...xyz ですShow me the sharing settings and permission list for Google Drive file ID 1abc...xyzアクセス権確認: ファイルID 1abc...xyz に誰がアクセスできるか権限一覧を出してname: drive-get-permissions description: Google Drive のファイルの共有設定を確認する。「共有状況確認」「誰がアクセスできる」「共有設定を見せて」「アクセス権確認」「権限一覧」「共有中のユーザー」などで起動。 allowed-tools: [Read, Bash]
Drive Get Permissions
Google Drive のファイルの共有設定を確認します。
引数
- ファイルID (必須): 共有設定を確認するファイルのID
実行方法
python plugins/shiiman-google/skills/drive-list/scripts/google_drive.py permissions --file-id <file-id>
使用例
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: 共有相手のメールアドレス
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/check-google-drive-file-permissions-mmh8qqri/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/check-google-drive-file-permissions-mmh8qqri' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/check-google-drive-file-permissions-mmh8qqri/download' --output '.skill-downloads/check-google-drive-file-permissions-mmh8qqri/SKILL.md.part' && mv '.skill-downloads/check-google-drive-file-permissions-mmh8qqri/SKILL.md.part' '.skill-downloads/check-google-drive-file-permissions-mmh8qqri/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/check-google-drive-file-permissions-mmh8qqri/SKILL.md' && test -s '.skill-downloads/check-google-drive-file-permissions-mmh8qqri/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/drive-get-permissions' && cp -R '.skill-downloads/check-google-drive-file-permissions-mmh8qqri' '.claude/skills/drive-get-permissions'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/check-google-drive-file-permissions-mmh8qqri'openskills read 'check-google-drive-file-permissions-mmh8qqri'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/check-google-drive-file-permissions-mmh8qqri/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
DeFi AMM Security
Security
Security checklist for Solidity AMM contracts, liquidity pools, and swap flows. Covers reentrancy, donation attacks, oracle manipulation, slippage, and integer math.
Semgrep Rule Creator
Security
Creates custom Semgrep rules for detecting security vulnerabilities, bug patterns, and code patterns. Includes test-first methodology, taint mode support, and validation steps. Helps when building targeted static analysis detections.
Dev Toolbar Review Guide
Security
Safety rules for the dev toolbar, PostHog client, and feature flags. Use when reviewing changes to dev-tools and related files, covering environment guards, override cookies, and SSE stream safety.