adobe-policy-guardrails
Analyze and enforce repository, runtime, data, spend, endpoint, and approval guardrails without guessing secret formats or content-policy rules
Install / Use
npx skills add jeremylongshore/tons-of-skills-marketplace --skill adobe-policy-guardrailsInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of adobe-policy-guardrails
adobe-policy-guardrails scores 83/100 on our quality scale, 3035th of 4,700 Development & Engineering skills we index.
Its SKILL.md is 4.2 KB long, well organised into 13 sections and no code examples: a solid amount of guidance for an agent.
With 2,785 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so adobe-policy-guardrails is actively maintained.
- Our last check on 2026-11-06 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
adobe-policy-guardrails compared with similar skills
All 4 of these similar skills score higher than adobe-policy-guardrails; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| adobe-policy-guardrails (this skill)by jeremylongshore | 83 | 2.8k | 53d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install adobe-policy-guardrails?
- Run
npx skills add jeremylongshore/tons-of-skills-marketplace --skill adobe-policy-guardrails. The install tabs above show the steps for each supported agent. - Which AI agents does adobe-policy-guardrails work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is adobe-policy-guardrails safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is adobe-policy-guardrails still maintained?
- The repository was last updated about 2 months ago, so adobe-policy-guardrails is actively maintained.
Skill content
View source on GitHubname: adobe-policy-guardrails description: >- Analyze and enforce repository, runtime, data, spend, endpoint, and approval guardrails without guessing secret formats or content-policy rules. Use when the task requires adobe policy and execution guardrails. Trigger with "Adobe guardrails", "block unsafe Adobe calls", or "Adobe policy checks". allowed-tools: Read,Glob,Grep,Write,Edit argument-hint: "<repository-or-service> <operations> <policy-owners>" version: 1.8.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io tags: [saas, adobe, guardrails] model: inherit effort: high compatibility: "Designed for Claude Code; live Adobe actions require network access, appropriate entitlement and authentication, and explicit approval"
Adobe Policy and Execution Guardrails
Overview
Analyze and enforce repository, runtime, data, spend, endpoint, and approval guardrails without guessing secret formats or content-policy rules. This workflow produces a reviewable artifact and evidence before any live side effect.
Prerequisites
- Current first-party Adobe documentation for every selected service, API version, auth flow, limit, and lifecycle.
- Named product, identity, security, data, budget, release, and operations owners appropriate to the scope.
- Synthetic or approved non-production fixtures with secret and content canaries.
Current Contract
Guardrails derive from current service docs and local policy: approved auth flows, hosts/versions, scopes/profiles, schemas, storage domains, budgets, data classes, and approval boundaries. Secret prefixes and prompt regexes are not authoritative security or content-policy controls. Recheck the dated evidence map before relying on mutable product behavior.
Authentication
Use mature secret scanners plus entropy/context rules and provider revocation procedures. Runtime authorization evaluates credential binding, entitlement, resource, operation, and approval.
Instructions
- Inventory all Adobe calls, credentials, endpoints, versions, payload classes, storage URLs, retries, jobs, events, and destructive operations.
- Create allowlists for current hosts/versions/services and denylists for JWT, /sensei/cutout, and retired Lightroom Firefly Services.
- Validate configuration/request/response schemas and redact tokens, signed URLs, prompts, and customer content.
- Enforce data-purpose, owner, budget, concurrency, idempotency, and approval tokens before side effects.
- Route Adobe policy outcomes to a human-readable denial path; never silently rewrite prompts or broaden scopes.
- Test bypasses, stale docs, false positives, emergency disablement, exception expiry, and audit receipts.
Tool Discipline
Use Read, Glob, and Grep to inspect current documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Skill invocation alone does not authorize network access, credentials, Adobe content, consent, uploads, generation, spend, deployment, registration changes, replay, cancellation, or deletion.
Approval Boundaries
Security/product/data/budget owners approve policy and exceptions. Generation, upload, deploy, webhook change, cancellation, replay, and deletion remain independently approved actions.
Error Handling
- Do not claim Adobe secrets always have a specific prefix.
- Do not claim local regexes predict Firefly policy decisions.
- Fail closed when endpoint/version or approval evidence is unknown.
Output
Return policy sources, allow/deny rules, enforcement points, test corpus, exceptions, receipts, drift monitor, and owners. Mark assumptions, observed environment behavior, owners, evidence dates, and unresolved gaps explicitly.
Examples
- Block /sensei/cutout before network execution.
- Detect a signed URL in a log fixture and fail the gate.
Validation
Exercise and record expected and observed results for:
- obsolete route
- unknown host
- secret leak
- policy outcome
- budget ceiling
- expired exception
Resources
- Current first-party evidence map — recheck dated Adobe sources before execution.
- Treat observed tenant or product behavior as environment-specific evidence, never a universal Adobe guarantee.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
