'permis' 검색 결과

Review Windows privilege escalation paths from a standard user session to Administrator or SYSTEM. Examine service permissions, token privileges, library loading, scheduled tasks, and stored credentials, with detection indicators for defensive validation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating privilege escalation in authorized Windows assessments
• Reviewing service and scheduled task permissions
• Checking detection coverage with attack and defense teams

Assess Kubernetes security from an existing pod or API access point. Covers permission checks, exposed node services, secrets, host access, and cloud metadata to explain how configuration weaknesses can expand access across a cluster.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review service account permissions and RBAC settings
• Assess host access and secrets exposure from pods
• Trace access paths from a cluster to cloud infrastructure

Create and manage Solana asset vaults with GLAM Protocol through its CLI or TypeScript SDK. Configure delegated permissions, manage investor subscriptions and redemptions, and use integrations for token swaps, lending, staking, and USDC transfers between chains.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a tokenized vault and manage subscriptions and redemptions
• Delegate trading permissions for specific protocols
• Swap tokens with Jupiter or lend through Kamino

Coordinate transactions between AI agents by connecting counterparty checks, negotiation, payment, escrow, and dispute handling. This entry skill selects relevant protocol guides and integrations, helping define permissions and agree how contested work or payments will be reviewed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check a paid API's provider, price, and terms
• Design spending permissions that can be revoked
• Arrange escrow and a review path for disputed work

Troubleshoot Feishu plugin authorization and permission problems using an FAQ and a diagnostic command. Check account configuration, API connectivity, app permissions, and user authorization, then review a report with issues and suggested fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate errors that persist after repeated authorization
• Review app permissions and user authorization together
• Check account configuration and API connectivity

Diagnose command failures before attributing them to sandbox restrictions, which limit access to files and networks. Check execution methods, command matching, and network behavior, then prepare an evidence-based report for the person responsible for settings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating permission errors such as EPERM
• Separating network restrictions from hostname failures
• Checking why an excluded command still fails

Investigate cloud configuration weaknesses across AWS, GCP, and Azure, including public storage, exposed services, and leaked credentials. Find candidates in public information and JavaScript, then verify data access and permissions to establish practical impact.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking public access to S3, GCS, and Azure Blob storage
• Reviewing exposed serverless and managed services
• Assessing CloudWatch RUM guest role permissions

Launch a new bb agent thread with the intended project, model, permissions, and task brief. It sets up a separate working copy when needed, checks the assigned permissions, and reports the resulting thread configuration.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Launching a standalone bb agent
• Assigning a subtask in a separate working copy
• Starting a read-only investigation worker

Review a Marin access-change pull request by decrypting user identities and explaining their roles and resources. After explicit human confirmation, merge the request and apply only the verified permission changes through Pulumi.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking who receives access in an encrypted grant request
• Reviewing roles and resources before approving access
• Applying confirmed permission additions or revocations

Guide authorized testing of business logic flaws, such as skipped payment steps, altered prices, concurrency issues, and permission errors. The skill helps define boundaries, choose further investigation paths, and organize reproduction evidence and business impact assessments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Defining the scope of business logic testing
• Choosing further checks for payment and permission flows
• Organizing reproduction steps and business impact evidence

Analyze permission prompts and auto mode denials, then generate permission rules and autoMode entries that cut prompt fatigue. Use when prompts keep interrupting, auto mode falls back to prompting, or after sessions with many denials.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[Deprecated] This is the required documentation for agents operating on the CloudBase Relational Database through MCP. It defines the canonical SQL management flow with `queryMysqlDatabase`, `manageMysqlDatabase`, `queryPermissions`, and `managePermissions`, including destroy flow, async status checks, safe query execution, schema initialization, and permission updates. MySQL provisioning is no longer available through MCP; new environments should use PostgreSQL — see postgresql-development skill instead.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Recommend safe Bash permissions for Elixir mix commands in; Use when permission prompts slow workflow, "fix…

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Skill permission analysis, one-time authorization, analyze skill permissions, batch authorization

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when implementing or debugging Formax permissions/policy/approval behavior and UI (allow/ask/deny rules, workspace boundaries, approval prompts, and /permissions overlay parity with Claude Code).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reduce repeated permission prompts across Microsoft Scout, Copilot CLI, and host tool confirmations with user-approved settings and explicit before/after verification. Use when users ask for permission max, fewer approval prompts, shell allow-list expansion, autoApprove, or diagnosis of repeated Read/Write/PowerShell confirmations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill to create, deactivate, freeze, or manage Salesforce users, assign user licenses and feature licenses, configure profiles and roles, set login hours and IP restrictions, and set up delegated administration. Triggers: 'add a new user in Salesforce', 'create a user and assign a licence', adding a new user, deactivating a departing employee, license assignment, freezing a user account, delegated admin setup. NOT for designing the permission set / PSG model — use admin/permission-set-architecture. NOT for who can see which records — use admin/sharing-and-visibility. Also covers: bulk user loads by CSV, Bulk API 2.0 upsert on Username, the UserLogin freeze object, licence and permission-set-licence reclamation, Role metadata deployment, and the offboarding checklist as SOQL.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when configuring OmniStudio at the org level: enabling Standard Runtime, selecting the Runtime Namespace, assigning Permission Set Licenses, toggling feature settings, and granting Experience Cloud community access. Trigger keywords: OmniStudio Settings, Standard OmniStudio Runtime, managed package runtime, runtime namespace, OmniStudio Permission Set, OmniStudio PSL. NOT for moving an org off the vlocity namespace — use omnistudio/vlocity-to-native-omnistudio-migration. NOT for deciding whether to adopt OmniStudio — use architect/omnistudio-vs-standard-decision.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Author the Salesforce Configuration Workbook — the structured, reviewable handoff document an admin uses to execute a feature across Objects/Fields, Page Layouts, Profiles/PSGs, Sharing, Validation, Automation, List Views, Reports, Integrations, and Data. Triggers: 'salesforce configuration workbook', 'admin handoff document', 'implementation workbook'. NOT for object design itself (use admin/custom-field-creation, admin/lookup-and-relationship-design, agents/object-designer/AGENT.md), NOT for permission set design (use admin/permission-set-architecture, agents/permission-set-architect/AGENT.md), NOT for Flow construction (use skills/flow/* and agents/flow-builder/AGENT.md), and NOT for the deployment manifest (use skills/devops/metadata-api-retrieve-deploy). More triggers: workbook row schema, recommended_agent, recommended_skills, row_id, source_req_id, RTM linkage block, not-in-scope-this-release, descope ledger, version-lock the workbook, check_workbook.py.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when enabling Data Cloud (Data 360) in an org, creating data spaces, assigning permission sets, registering ingestion API sources, or configuring activation targets. Triggers: 'enable data cloud', 'data spaces setup', 'data cloud permission sets', 'ingestion API connected app', 'activation target setup', 'data cloud licensing', 'dedicated home org vs existing org'. NOT for data streams or DLO-to-DMO mapping — use data/data-cloud-data-streams. NOT for identity resolution rulesets — use admin/data-cloud-identity-resolution.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configure CRM Analytics (formerly Einstein Analytics) app sharing, dataset-level permissions, row-level security predicates, sharing inheritance, and license assignment. Trigger keywords: CRM Analytics security, row-level security predicate, dataset permissions, analytics sharing inheritance, Analytics Plus license. NOT for OWD and sharing rules — use admin/sharing-and-visibility. NOT for predicate design across many datasets — use architect/analytics-security-architecture.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Detects over-broad permission requests where a narrower permission or privacy-preserving alternative API is sufficient, violating Guideline 5.1.1(iii) data minimization requirements.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Adds or changes allowed commands in AI agent permission configs for OpenCode and Claude Code. Use when a command needs adding to an agent's allow list, when permission settings for existing commands need changing, when setting up a new AI tool that requires command permissions, or when the user asks to stop being prompted for a particular command.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a macOS app needs a TCC permission or touches private data — the map of which API, Info.plist key, and entitlement each permission needs, pre-prompt explanation patterns, denied-state recovery with System Settings deep links, and honest privacy copy.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.