菜单
Use when: building or debugging Office 365 Users connector flows in a Power Apps Code App, including profiles, managers, direct reports, photos, searchForUsers, or openUsersHttpRequest.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when: building or debugging Power Platform for Admins V2 connector operations in a Power Apps Code App, including environments, backups, disaster recovery, environment groups, governance policies, capacity, billing, cloud flows, Copilot agents, Power Pages, or tenant administration.
Use when: performing an evidence-based security review of a Microsoft Power Apps Code App, especially checking external runtime sources, hard-coded passwords or secrets, security by obscurity, hard-coded access bypasses, DOM injection, and sensitive client-side data without reporting package, server, CSP-header, authentication-host, or infrastructure false positives owned by the Microsoft managed platform.
Start skill for new Code App project setup. Use this skill when starting a fresh app build or UI build so the agent confirms theme direction, offers mockups, and only then implements files.
Use when: building or debugging Microsoft Teams connector flows in a Power Apps Code App, including teams, channels, chats, mentions, tags, notifications, cards, meetings, transcripts, recordings, schedules, or the Teams HttpRequest helper.
Use when: adding or calling Power Automate cloud flows from a Power Apps Code App, including callFlow(...), generated flow services, or shared_logicflows connectionReferences.
Use when: building or debugging SharePoint list, attachment, library, or file flows in a Power Apps Code App, including list-id or environment-variable-based setup.
| name | office365-users |
| description | Use when: building or debugging Office 365 Users connector flows in a Power Apps Code App, including profiles, managers, direct reports, photos, searchForUsers, or openUsersHttpRequest. |
Do not use CLI PAC commands to get connecctor models or services,
use codeApp/dist/connectors/office365users.js as the repo source of truth.
Always read the current power.config.json before editing it.
Ensure "id": "/providers/Microsoft.PowerApps/apis/shared_office365users" exists.
"connectionReferences": {
"office365users": {
"id": "/providers/Microsoft.PowerApps/apis/shared_office365users",
"displayName": "Office 365 Users",
"dataSources": [
"office365users"
],
"authenticationType": null,
"sharedConnectionId": null,
"dataSets": {}
}
}
Rules for editing power.config.json:
sharedConnectionId, authenticationType, and other working connection metadata.Prefer the exported helper layer instead of wiring raw connector operations directly in app code.
callUsersOperation(operationName, parameters)openUsersHttpRequest(options)updateMyProfile(profile)getMyProfile(options)getUserProfile(userId, options)getManager(userId, options)getDirectReports(userId, options)getMyTrendingDocuments(options)getTrendingDocuments(userId, options)getRelevantPeople(userId)updateMyPhoto(bodyOrOptions, contentType)getUserPhotoMetadata(userId)getUserPhoto(userId)searchForUsers(options)getDirectReports(...) defaults to DirectReports_V2.getUserPhoto(...) uses UserPhoto_V2.searchForUsers(...) uses SearchUserV2.searchForUsers(...) accepts nextLink and skip aliases and converts them into skipToken.openUsersHttpRequest(...) maps friendly inputs to connector fields:
uri -> Urimethod -> Methodbody -> BodycontentType -> ContentTypecustomHeaders[0..4] -> CustomHeader1..5Use this only when no helper exists for the action you need.
skipToken or nextLink, not $skip.openUsersHttpRequest(...).