Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

android-permissions-activity-resultsAndroid 权限活动结果

Agent Skill

android-permissions-activity-results 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

240

周安装

10

GitHub Stars

5

下载量

80
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:android-permissions-activity-results(Android 权限活动结果)
来源仓库:https://github.com/krutikjain/android-agent-skills
仓库路径:skills/android-permissions-activity-results
安装命令:
npx skills add https://github.com/krutikjain/android-agent-skills --skill android-permissions-activity-results
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/krutikjain/android-agent-skills --skill android-permissions-activity-results

简介

用于查找、检索和筛选 Android 权限请求和活动结果相关信息。

  • 适用于权限请求流程、Activity Result API 和相机权限等场景。
  • 提供现代权限请求、能力门控 UX 和 API 级别行为的具体实现指导。
  • 安装命令:npx skills add https://github.com/krutikjain/android-agent-skills --skill android-permissions-activity-results
  • 注意权限范围和维护状态,避免触发不必要的联网或文件操作。

SKILL.md

Android Permissions Activity Results

When To Use

  • Use this skill when the request is about: android permission request flow, activity result api android, camera permission in android app.
  • Primary outcome: Use modern permission requests, Activity Result APIs, and capability-gated UX in Android flows.
  • Read references/patterns.md when you need the picker-vs-permission matrix or API-level behavior checklist.
  • Read references/scenarios.md for photo picker, notification permission, and limited media access examples.
  • Handoff skills when the scope expands:
  • android-media-files-sharing
  • android-testing-ui

Workflow

  1. Start with the capability the user needs, not the permission name: photo picker, document picker, camera capture, or notification opt-in often avoids broader runtime permissions.
  2. Choose the right Activity Result contract and keep the launcher in a stable lifecycle owner such as an activity, fragment, or remembered Compose launcher.
  3. Model the full permission state space explicitly: granted, denied, permanently denied, limited/selected access, one-time access, and settings-based recovery.
  4. Account for API-level differences such as POST_NOTIFICATIONS on Android 13+, approximate vs precise location, background location as a separate flow, and Android 14 selected-photos access.
  5. Re-check capability on return from settings or picker flows, then validate rotation, process death, and denial recovery instead of assuming the happy path.

Guardrails

  • Treat loading, empty, error, offline, and permission-denied states as first-class UI states.
  • Do not launch permission or picker contracts directly from composition without a user action or explicit side effect.
  • Prefer the narrowest capability surface available, such as Photo Picker or SAF, over broad storage permissions.
  • Keep permission recovery testable: rationale, settings redirect, denied state, and post-return revalidation.

Anti-Patterns

  • Assuming the happy path is enough for product flows.
  • Repeatedly re-prompting after denial instead of offering a clear settings or alternate-path recovery.
  • Requesting media or storage access when the Photo Picker or document contracts are enough.
  • Treating Android 14 selected-photos access as full media-library access.

Review Focus

  • Can the feature use a picker or contract instead of a runtime permission?
  • Does the flow handle denial, limited access, and return-from-settings correctly?
  • Are permission launches owned by the right lifecycle scope and initiated at the right time?
  • Are platform-specific behaviors called out for Android 13+ and Android 14+ where relevant?

Examples

Happy path

  • Scenario: Find the repo's Activity Result and permission surfaces before proposing a flow change.
  • Command: rg -n "rememberLauncherForActivityResult|RequestPermission|RequestMultiplePermissions|PickVisualMedia|OpenDocument|TakePicture" examples

Edge case

  • Scenario: Review notification and media access paths for API-level-specific behavior.
  • Command: rg -n "POST_NOTIFICATIONS|READ_MEDIA_|READ_EXTERNAL_STORAGE|PickVisualMedia" examples

Failure recovery

  • Scenario: Differentiate permission prompts from media-sharing and testing requests.
  • Command: python3 scripts/eval_triggers.py --skill android-permissions-activity-results

Done Checklist

  • The chosen contract or picker is narrower than a broad permission where possible.
  • Denied, permanently denied, limited, and settings-return states are all modeled.
  • API-level differences are called out for the affected Android versions.
  • Recovery UI and observability are explicit instead of implied.

Official References

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

37.31%
按下载量换算30

Claude

30.36%
按下载量换算24

Cursor

20.13%
按下载量换算16

Gemini CLI

9.94%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills