Results for “orphan”

Use this skill when the risk register and the statement of applicability were written separately and may not agree, and the team asks "do our risks link to our controls", "traceability between risk treatment and the SoA", "why is this control applicable", "the auditor could not trace a risk to a control", "check our risk treatment plan against the SoA" or "orphan controls". Checks in both directions that every treated risk points to controls and actions, and every applicable control traces back to a risk or obligation, then writes a traceability matrix and a list of orphans and contradictions with proposed fixes.

The English summary is being prepared. Showing the original description.

Tidy an agent's always-loaded memory index (MEMORY.md) on macOS or Linux: trim long lines, move closed entries to an archive, fold domains into hub files, restore dropped pins and add pointers for orphan memory files. Use when the index is over budget or has orphans. Triggers: /memory-tidy, /mt, tidy memory.

The English summary is being prepared. Showing the original description.

Use when the user asks to "plan my site structure", "design the page hierarchy / navigation / URL taxonomy", "fix internal linking", or "find orphan pages"; runs two modes — architecture (hierarchy, nav, URL patterns, hub/spoke clusters, Mermaid site maps) and linking (link graph, authority flow, anchor text, orphan disposition, source/target/anchor plan) — and outputs a structure score /100 plus a handoff summary. Not for external backlinks — use offsite-signal-analyzer; not for XML sitemap or indexation issues — use technical-seo-checker. 网站架构/信息架构/站点地图/内链优化

The English summary is being prepared. Showing the original description.

Govern Power Automate flows and Power Apps at scale using the FlowStudio MCP cached store. Classify flows by business impact, detect orphaned resources, audit connector usage, enforce compliance standards, manage notification rules, and compute governance scores — all without Dataverse or the CoE Starter Kit. Load this skill when asked to: tag or classify flows, set business impact, assign ownership, detect orphans, audit connectors, check compliance, compute archive scores, manage notification rules, run a governance review, generate a compliance report, offboard a maker, or any task that involves writing governance metadata to flows. Requires a FlowStudio for Teams or MCP Pro+ subscription — see https://mcp.flowstudio.app

The English summary is being prepared. Showing the original description.

Analyze and improve the internal link structure of an AEM Edge Delivery Services site. Builds a link graph from the query index and page content, identifies orphan pages, hub pages, and content silos, and generates specific linking recommendations with suggested anchor text and placement. Use when improving site navigation, fixing orphan pages, strengthening topical authority, or auditing link equity distribution.

The English summary is being prepared. Showing the original description.

Detects data integrity issues including orphaned records, broken foreign key relationships, constraint violations, and provides automated fix migrations. Use for "data integrity", "orphaned records", "broken relationships", or "data quality".

The English summary is being prepared. Showing the original description.

Review Claude Code settings for duplicate skills, outdated memory files, unused permissions, and other clutter. The workflow presents evidence for each candidate, requests individual approval, and records reversible cleanup actions.

• Reviewing overlaps after installing many skills
• Checking outdated memory files and unused hooks
• Organizing duplicate permission entries

Audit an LLM Wiki for conflicting or outdated claims, broken links, missing concept pages, weak sources, and index inconsistencies. Return findings grouped by severity with evidence and suggested fixes, leaving page content unchanged.

• Checking wiki pages for contradictions and outdated claims
• Finding broken links and isolated pages
• Reviewing sources and missing concept explanations

Find important pages that receive no links from elsewhere on the site. Compare crawl results with sitemaps and indexed pages, then suggest relevant existing pages where descriptive internal links could help connect the content.

• Audit internal links across a site
• Investigate pages with low organic search traffic
• Find relevant pages to link to isolated content

Inspect stored Muse records when regular product tools do not reveal enough detail. Use read-only database queries to investigate missing records, trace execution history, and check relationships or inconsistencies across different product areas.

• Investigating missing or orphaned records
• Reconstructing execution history
• Tracing relationships across product areas

Audit GitHub issues to find open work outside a masterplan, distinguishing missing parents from missing plan ancestors. Preview or apply removal of closed issues from the hierarchy while keeping their open children connected to the plan.

• Finding open issues outside a masterplan
• Distinguishing missing parents from missing plan ancestors
• Checking issue organization in automation

Review AI-generated code for problems hidden behind successful runs. Check failure handling, resource cleanup, unusual inputs, nonexistent dependencies, and departures from project conventions to identify missing safeguards before merging or accepting the work as complete.

• Audit code after an AI generation session
• Review an AI-generated pull request before merging
• Investigate brittle code that appears to work

Design employee access management across multiple systems using HR records. This skill covers account changes when people join, move roles, or leave, along with role definitions, approval workflows, periodic access reviews, and cleanup of accounts left behind.

• Automating account changes for hires, transfers, and departures
• Finding accounts that remain after employees leave
• Reviewing overlapping roles and unnecessary permissions

Audit a gbrain knowledge base for outdated pages, broken or missing links, inconsistent tags, and missing citations. Get issue counts and specific repair actions, with additional checks for search quality and maintenance status.

• Audit knowledge base quality
• Find isolated pages and broken links
• Review citations and inconsistent tags

Recommend where new gbrain pages belong using the active schema pack, a configuration defining page types and storage paths. It also checks existing pages for missing or undeclared types and highlights cases requiring a classification decision.

• Choose a storage path before creating a brain page
• Check filing rules before a bulk import
• Apply classification settings for a specific source

Audit website structure, navigation, URLs, and internal links to produce prioritized fixes. For a new site or redesign, create a site tree, URL specifications, and redirect mappings that clarify how pages connect.

• Auditing an existing website's structure
• Planning navigation for a website redesign
• Connecting related pages with internal links

Checks how company strategy connects to department, team, and individual goals. Identifies disconnected or conflicting goals, missing ownership, departmental silos, and communication gaps, then guides workshops, shared measures, and quarterly reviews to restore alignment.

• Reviewing links between company and team goals
• Finding conflicts between departmental goals
• Assigning ownership to neglected company objectives

Analyze git history to map contributors to security-sensitive files, identify reliance on too few people, and find stale areas. Export CSV and JSON results for ownership reviews, graph exploration, and comparison with CODEOWNERS.

• Find stale security-sensitive code with few maintainers
• Check reliance on individual authentication or cryptography maintainers
• Compare CODEOWNERS with actual contribution history

Audit game asset files for naming rules, size limits, formats, and broken references. Receive a report of measured violations and suggested fixes, with clear explanations of checks that lack data or cannot be assessed for the engine.

• Checking image and audio naming conventions
• Finding files that exceed asset size limits
• Investigating missing references and potentially unused assets

Analyze git history to map contributors to security-sensitive files, identify reliance on too few people, and find stale areas. Export CSV and JSON results for ownership reviews, graph exploration, and comparison with CODEOWNERS.

• Find stale security-sensitive code with few maintainers
• Check reliance on individual authentication or cryptography maintainers
• Compare CODEOWNERS with actual contribution history

Run repeatable, read-only checks on an Obsidian wiki to find broken or ambiguous links, isolated pages, missing metadata, empty sections, outdated index entries, and source-record issues. Review findings with paths, line numbers, and counts.

• Finding broken links and isolated pages
• Auditing note metadata and source records
• Reviewing empty sections and outdated index entries

Analyze git history to map contributors to security-sensitive files and identify ownership gaps. Estimate bus factor, a measure of dependence on few people, group files that change together, and export CSV or JSON for further analysis.

• Finding sensitive code with stale, concentrated ownership
• Checking reliance on one person for authentication code
• Comparing CODEOWNERS with contribution history

Find classes left in parent folders or namespaces and identify nested component structures. Compare consolidation, splitting, and shared code extraction, then plan and carry out refactoring with updated references and tests.

• Find classes left in parent namespaces
• Compare consolidation and splitting of nested components
• Move shared utilities into a dedicated component

Stop stuck Ouroboros executions or background jobs by ID, or cancel all running and paused executions in the current project. It reports whether cancellation is complete or has been requested, with guidance for checking the final status.

• Stopping a stuck execution
• Cancelling a background job by ID
• Cancelling all active executions in a project