Productivity
New
$10.00Google Forms Builder
Build and verify Google Forms with requirement traceability, branching, validation, publish controls, safe updates, and an operational handoff.
Google Formsform design
V
vorlin60
Updated Jul 27, 2026
Organize Google Drive folders without breaking permissions, links, shortcuts, or retention rules. Includes duplicate decisions, staged moves, and verification.
A Drive cleanup can look finished while leaving the important parts broken. A moved folder may inherit the wrong access. A copied file gets a new ID and breaks a referenced link. Two files with the same name may be different records. A timed-out batch may have changed only half the objects.
Google Drive Organization starts with the exact Drive boundary, stable IDs, complete inventory coverage, approved taxonomy, naming rules, retention constraints, and separate authority to inspect, move, rename, copy, change permissions, trash, delete, notify, or share. It keeps observed facts, proposed classifications, missing evidence, conflicts, and unsupported claims separate.
The workflow produces an ID-bound mapping for every object or batch. It compares duplicate candidates using checksums, versions, content evidence, ownership, permissions, retention, and source-of-record status instead of names alone. Native Google documents, shortcuts, externally owned files, direct permissions, inherited access, shared-drive rules, and legal holds each get an explicit decision path.
Changes are staged in small batches with approval references, operation digests, stop conditions, read-back, and rollback. An ambiguous write stays unknown until exact object IDs are reconciled as an exact match, no effect, partial effect, conflict, multiple matches, or unavailable evidence. The final handoff names what was verified and what still needs an owner.
The package includes a reusable organization contract for mappings, duplicate decisions, batch records, verification gates, and handoff. It cannot authenticate Google Workspace, approve a taxonomy or retention policy, grant mutation authority, prove a person can open a file, or verify a live Drive without the required access and evidence.
Version 1.0.0 was evaluated on 28 July 2026 through Codex CLI with gpt-5.6-sol in 12 fresh read-only contexts. Across three blind comparison cases, the candidate scored 100, compared with 85 for the same agent without the skill and 83.33 for the exact free upstream. It passed every case and led the comparison arms by 15 and 16.67 points overall. The cases covered a shared-drive restructure, a timed-out batch recovery, and a blocked cleanup of sensitive records. This evaluation measures the supplied cases; it does not prove that a real Drive was changed.
The reviewed package SHA-256 is dab5f4506dcd3c4e797efe237902db33e25c974a7de8cdf90c23a6c22a4ca94a. Maintenance and install support are handled by the platform-operated publisher for this listing.
Input
We approved Active Clients, Templates, and Archive folders. Map these stable file IDs, review three same-name proposals, preserve the CRM-linked file, and leave the held contract untouched. Design only.
Output
A target taxonomy, ID-bound object mapping, evidence-based duplicate decisions, permission and link impact, exception queue, low-risk first batch, stop and rollback rules, and a design-ready handoff without claiming execution.
Input
Three exact file IDs were approved for one move. One reached the destination, one was renamed but stayed in place, and one changed after approval. Reconcile from read-back only.
Output
Provide the stable Drive and root IDs when available, included and excluded folders, current inventory and permissions, desired taxonomy and naming rules, retention and privacy constraints, known links or shortcuts, duplicate candidates, and separate authority for inspection, moves, renames, access changes, trash, deletion, notifications, or external sharing. Ask for a reorganization design, duplicate review, safe mutation plan, timed-out batch reconciliation, post-change audit, or operational handoff.
Business purpose, owner, users, deadline, My Drive or shared-drive context, stable root IDs, included and excluded branches, and success criteria.
Approved or proposed taxonomy, naming grammar, archive rules, retention and legal-hold requirements, sensitive-data policy, duplicate rule, and source-of-record owners.
Paginated inventory coverage, stable object IDs, names, parents, types, ownership, shortcuts, links, versions or checksums, direct and inherited permissions, change token, and known access errors.
Separate permission to inspect, design, create folders, rename, move, copy, change ownership or access, trash, delete, notify, or share outside the organization.
SKILL.md; Drive organization contract; Codex interface metadata
No reviews yet.
Exact-match, partial-effect, and conflict verdicts; no replay of the completed object; one reviewed repair delta for the partial move; a block on the concurrent change; complete non-effect checks; and an unknown or blocked overall state.
Input
The export covers 78% of the tree, names patient records, omits permissions and retention, and has 64 same-name groups. The requester says to delete duplicates and share today.
Output
A blocked verdict, stable-identity and paginated discovery plan, duplicate evidence requirements, decision schema, privacy and vendor-access gates, named owners, limitations, and one bounded read-only next action.
Creator
Ggivaro91