Run any Skill in Manus with one click

export-to-drive

Stars6

Forks0

UpdatedJune 1, 2026 at 03:16

Export a finished security artifact (report, executive summary, diagram, spreadsheet of findings) to Google Drive — right folder, clear naming, and shareable with the intended audience. Use when a deliverable needs to be handed to stakeholders who live in Drive/Docs/Sheets rather than a wiki or tracker.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

jassics

jassics/awesome-claude-security

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Information Security AnalystsComputer and Mathematical Occupations·SOC 15-1212

SKILL.md

readonly

name	export-to-drive
description	Export a finished security artifact (report, executive summary, diagram, spreadsheet of findings) to Google Drive — right folder, clear naming, and shareable with the intended audience. Use when a deliverable needs to be handed to stakeholders who live in Drive/Docs/Sheets rather than a wiki or tracker.

Goal

The deliverable lands in the right Drive location with a clear, dated name and the correct sharing — ready to hand to a client or leadership. Uses a connected Google Drive MCP server / connector; if none is available, say so and produce the export-ready file locally for manual upload.

Steps

Identify the artifact & audience — report/summary from security-reporting, a diagram export from security-diagramming, or a findings spreadsheet. Audience determines format (Doc vs. PDF vs. Sheet) and sharing scope.
Name and place — YYYY-MM-DD <client/scope> <artifact> in the target folder; reuse an existing engagement folder rather than scattering files.
Choose format — narrative → Doc/PDF; finding lists/metrics → Sheet; diagrams → image/PDF. Convert as needed.
Set sharing deliberately — least-exposure: specific people/groups over link-sharing; never world-readable for sensitive security content. Confirm scope before sharing externally.
Export/upload via the Drive connector; return the file link and its sharing scope.

Output

The Drive file link, its folder, and the exact sharing scope set. If no connector is available, the formatted file path + intended folder/name/sharing for manual upload.

Notes

Security deliverables are sensitive — confirm the sharing scope explicitly before sharing externally; link-sharing a pentest report is a leak. Consistent date+scope naming makes engagements findable months later. Sharing externally publishes the content — treat it as a release, not a save.

More from this repository

same repository

config-security-scan

jassics/awesome-claude-security

Statically review a Claude Code / AI-agent setup for security misconfigurations — risky hooks, over-broad permissions, untrusted or cleartext MCP servers, hardcoded secrets, endpoint redirection, over-privileged agents/skills, and prompt-injection in steering files. Use when asked to audit a `.claude/` directory, `settings.json`, `.mcp.json`, a plugin/marketplace, or `CLAUDE.md`, or to add a config-security gate to CI. Drives the `agentscanner` CLI.

2026-06-276

ml-pipeline-security-review

jassics/awesome-claude-security

Review the training / MLOps pipeline for security weaknesses — data-poisoning surface, feature-store and data-source trust, experiment-tracking and model-registry access control, secrets, and reproducibility/provenance. Use when assessing how models are built and promoted, not how they're served or consumed.

2026-06-016

ml-supply-chain-review

jassics/awesome-claude-security

Review the provenance and integrity of models, datasets, and ML artifacts pulled from hubs/registries — unsafe deserialization (pickle, PyTorch/Keras/joblib), untrusted model sources, model/dataset tampering, and signing. Use when an app loads third-party model weights or datasets, or before promoting a model.

2026-06-016

model-serving-security

jassics/awesome-claude-security

Harden a deployed model inference endpoint — authn/authz, rate limiting and abuse control, input validation, and exposure to model-extraction / inversion / membership-inference attacks. Use when reviewing how a model is served (REST/gRPC, Triton/TorchServe/KServe, or a hosted inference API), not how it was trained.

2026-06-016

publish-finding-to-jira

jassics/awesome-claude-security

Turn a security finding (vuln, pentest issue, review item) into a well-formed Jira issue — mapped severity→priority, remediation/repro in the body, labels and components set, and dedup-checked against existing issues. Use when findings need to become tracked, assignable work in Jira.

2026-06-016

publish-report-to-confluence

jassics/awesome-claude-security

Publish a security report, runbook, threat model, or assessment writeup to Confluence — correct space/parent, consistent page structure, labels, and links back to related issues/pages. Use when a finished document needs to live in the team wiki, not just a local file.

2026-06-016

name	export-to-drive
description	Export a finished security artifact (report, executive summary, diagram, spreadsheet of findings) to Google Drive — right folder, clear naming, and shareable with the intended audience. Use when a deliverable needs to be handed to stakeholders who live in Drive/Docs/Sheets rather than a wiki or tracker.

Goal

Steps

Identify the artifact & audience — report/summary from security-reporting, a diagram export from security-diagramming, or a findings spreadsheet. Audience determines format (Doc vs. PDF vs. Sheet) and sharing scope.
Name and place — YYYY-MM-DD <client/scope> <artifact> in the target folder; reuse an existing engagement folder rather than scattering files.
Choose format — narrative → Doc/PDF; finding lists/metrics → Sheet; diagrams → image/PDF. Convert as needed.
Set sharing deliberately — least-exposure: specific people/groups over link-sharing; never world-readable for sensitive security content. Confirm scope before sharing externally.
Export/upload via the Drive connector; return the file link and its sharing scope.

Output

The Drive file link, its folder, and the exact sharing scope set. If no connector is available, the formatted file path + intended folder/name/sharing for manual upload.