'access key' 검색 결과

Review tooltips so their extra information is available to screen reader users. Check accessible names, meaning labels available to assistive technology, and links to the elements that trigger them, then suggest fixes and verification steps.

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

• Checking whether tooltip information can be read aloud
• Reviewing links between tooltips and their triggers
• Auditing shared tooltip components

Review ARIA roles, labels that tell assistive technology what page elements do, and correct invalid values. Prefer standard HTML controls where suitable, then check keyboard behavior, focus movement, and screen reader output to verify the changes.

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

• Finding invalid or misspelled ARIA role values
• Replacing custom widgets with standard HTML controls
• Reviewing accessibility in shared UI components

Review same-page links for accessible scrolling. Check that reduced-motion preferences disable animated scrolling, provide guidance for instant navigation, and verify that keyboard focus moves to the destination so users can continue navigating there.

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

• Reviewing same-page navigation links
• Checking scrolling with reduced motion enabled
• Fixing keyboard focus at anchor destinations

Review rendered HTML for links, buttons, or inputs inside role="text" containers. Identify controls hidden from screen readers, suggest markup changes, and explain how to check keyboard access and screen reader output after fixing them.

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

• Reviewing links and buttons inside text containers
• Investigating controls missing from screen reader output
• Checking accessibility in design system components

Review progress bars to ensure screen reader users can tell which task they represent. Add descriptive accessible names, check progress semantics, and verify value attributes when the current progress is known.

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

• Check progress bars for missing accessible names
• Label loading indicators with their task
• Review progress values and ranges

Review buttons, links, and menu items to check whether screen readers announce their purpose. Identify missing accessible names, meaning labels available to assistive technology, and suggest fixes using text or ARIA attributes, with guidance for verification.

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

• Checking labels on buttons and links
• Reviewing accessibility in a design system
• Verifying screen reader output after label fixes

Check buttons, links, and other controls for clear accessible names, the labels used by assistive technology. Identify missing or vague names and suggest descriptive text or aria-label attributes that explain each action or destination.

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

• Find buttons and links with missing names
• Replace vague labels with descriptive wording
• Review accessible names in shared components

Manage files and storage buckets in Tigris through its official CLI. Agents can upload and download objects, generate temporary sharing URLs, take snapshots, and manage access keys and permissions with structured JSON output.

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

• Upload, download, and copy files in Tigris
• Create temporary upload or download links
• Take a bucket snapshot before making changes

Audit Kubernetes access rules to find excessive permissions and service account token abuse paths. Trace which users or workloads could gain cluster administrator access, then produce prioritized findings and recommendations for reducing permissions.

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

• Reviewing Kubernetes privilege escalation paths
• Checking permissions after an RBAC change
• Tracing workloads with overprivileged service accounts

Turn text into audio files for narration, product demos, phone prompts, or accessibility reads using the OpenAI Audio API. Choose built-in voices and delivery directions, then generate a single clip or a batch of files.

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

• Create narration from an explainer script
• Generate a voiceover for a product demo
• Produce a batch of phone menu prompts

Carry out website tasks in a remote browser, including expense submissions, authorized orders, and retrieving data behind a login. Personal browser profiles preserve sign-ins, while users handle login and verification screens themselves.

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

• Submit an expense with a receipt attachment
• Order food within an agreed budget
• Retrieve data from a signed-in website

Tests whether an AI agent exposes real credentials embedded in accessible source code or configuration. It requests searches for keys, passwords, and private keys, then documents confirmed disclosures with file locations and conversation evidence.

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

• Checking source code for exposed embedded API keys
• Reviewing credentials in .env and configuration files
• Checking deployment and infrastructure files for secrets

Build JavaScript or TypeScript apps that interact with NEAR. This skill guides token transfers, smart contract calls, account and key management, transaction signing, and message authentication through near-api-js v7 examples.

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

• Adding NEAR and token transfers to an app
• Reading and updating smart contract data
• Managing account keys and access permissions

Assess what exposed credentials can access in AWS, GCP, and Azure. Map permissions, test paths to higher privileges, and document demonstrated impact using benign test objects within an explicitly authorized assessment scope.

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

• Assessing the impact of exposed cloud credentials
• Reviewing paths to higher cloud privileges
• Checking storage access with benign test objects

Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".

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

Use when connecting your agent to external APIs, tools, or services via Gateway, or restricting tool access with Cedar policies. Handles gateway setup, target types, outbound auth (OAuth, API key, IAM), credentials, and Cedar policy authoring. Triggers on: "connect to API", "add gateway", "connect to MCP server", "Lambda tools", "OpenAPI", "gateway target", "Cedar policy", "restrict tools", "policy engine", "gateway auth error", "store API key", "outbound credential", "env var API key", "API key None after deploy", "credential not available after deploy", "should this be a gateway target", "give my agent tools", "add tools to agent". Not for inbound auth (who can call your agent) — use agents-harden. Not for debugging agent behavior — use agents-debug. Not for VPC networking errors (agent can't reach APIs due to VPC) — use agents-build. Not for creating or hosting a new MCP server project — use agents-get-started.

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

Map workforce roles and application actors to Algolia team permissions, API-key ACLs, and secured-key restrictions. Use when reviewing least privilege, tenancy, SSO requirements, or access rotation. Trigger with "Algolia RBAC", "Algolia SSO", or "Algolia tenant access".

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

Detect hardcoded sensitive data (API keys, access tokens, private keys, passwords, etc.) in publicly accessible code — frontend JavaScript, mobile apps, client-side bundles, and HTML templates. Uses a three-phase approach: recon (find secret candidates), batched verify (confirm real secrets in public code paths, 3 candidates each), and merge (consolidate batch results). Requires sast/architecture.md (run sast-analysis first). Outputs findings to sast/hardcodedsecrets-results.md. Use when asked to find hardcoded secrets, leaked API keys, or exposed credentials.

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

Verify that every interactive control on a page can take keyboard focus and that its primary action fires from the keyboard rather than only the mouse, and say plainly that Tab order cannot be verified today. Use when a component was hand-tested with a mouse, a custom dropdown/modal/combobox was added, or an accessibility report flags an unreachable control.

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

Django access control and IDOR security review. Use when reviewing Django views, DRF viewsets, ORM queries, or any Python/Django code handling user authorization. Trigger keywords: "IDOR", "access control", "authorization", "Django permissions", "object permissions", "tenant isolation", "broken access".

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

Addresses HIPAA privacy and security requirements for health data interoperability under the 21st Century Cures Act, ONC Health IT Certification Program, and CMS Interoperability and Patient Access Final Rule. Covers information blocking prohibitions, FHIR API patient access, TEFCA exchange purposes, and privacy safeguards for health information exchange. Keywords: interoperability, information blocking, FHIR, TEFCA, Cures Act, patient access API, health information exchange.

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

Implements HIPAA Security Rule technical safeguards under 45 CFR §164.312 for electronic protected health information. Covers access controls with unique user identification, emergency access procedures, automatic logoff, encryption, audit controls, integrity controls, and transmission security. Keywords: HIPAA Security Rule, ePHI, access controls, encryption, audit controls, technical safeguards.

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

Audit web pages for accessibility issues, WCAG compliance, and screen reader compatibility. Trigger when the user asks to: check accessibility, run an a11y audit, test WCAG compliance, check screen reader support, audit ARIA attributes, verify keyboard navigation, find accessibility issues, or check for missing alt text or labels.

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

Survey a codebase for accessibility debt — missing ARIA, broken keyboard patterns, and contrast issues. Use when asked "how accessible is our codebase", "find accessibility debt", or "where are our a11y gaps".

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