3.7K skills · sorted by relevance
Get guidance on setting up OpenKnowledge for shared Markdown editing, sharing a project with collaborators, and previewing individual files. Explains setup commands and viewing options for agent environments, Claude Desktop, and the macOS desktop app.
Adjust .NET MAUI layouts to avoid system bars, screen cutouts, and keyboards, or extend content to screen edges. It covers .NET 10 safe area APIs, migration from older settings, and CSS coordination for Blazor Hybrid.
Use this skill when setting up, configuring, or managing Salesforce Lightning Knowledge — enabling the feature, designing record types on Knowledge__kav, configuring Data Categories for organization and visibility control, setting up publishing workflows, and layering approval processes. Trigger keywords: Lightning Knowledge setup, Knowledge article record types, Data Category visibility, Knowledge publishing workflow, Knowledge__kav configuration. NOT for converting Classic Article Types to Lightning — use admin/knowledge-classic-to-lightning. NOT for bulk-loading articles from an external help center — use data/knowledge-article-import. NOT for sizing the taxonomy itself (how many groups, how deep) — use architect/knowledge-taxonomy-design.
The English summary is being prepared. Showing the original description.
Work with documents in OpenKnowledge through its MCP tools, which connect agents to the knowledge base. Search and edit Markdown, use templates, check internal links, and inspect version history while keeping claims connected to preserved sources.
Organize a knowledge base into preserved sources, draft research, and stable articles. Follow rules for document status, cross-links, replacement history, and change logs so established knowledge remains traceable to its original evidence.
Organize knowledge notes with links that explain their relationships, search saved information, review conflicting claims, and prepare weekly digests. Retrieve earlier work sessions and conversations by topic or date to recover context before continuing a task.
Create and maintain knowledge collections in Open Knowledge Format v0.2, a Markdown format agents can read. Covers document types, source citations, verification records, indexes, and change logs, plus guidance for interpreting conformance warnings.
Design AI agent analytics workflows across distributed tables and documents. Combine Knowledge Catalog for metadata, meaning information about data and its usage rules, with managed Spark processing to produce architecture diagrams, deployment guidance, and validation plans.
Create, validate, and enrich Open Knowledge Format (OKF) bundles — the open spec for representing organizational knowledge as markdown files with YAML frontmatter. Use when the user mentions 'OKF', 'Open Knowledge Format', 'knowledge bundle', 'OKF bundle', 'create a knowledge base for agents', 'validate OKF', 'convert to OKF', 'enrich knowledge docs', 'agent-readable knowledge', 'LLM wiki', 'knowledge catalog', 'kcmd', or wants to structure knowledge as markdown files for AI agent consumption. Also use when the user has a directory of markdown files and wants to make them interoperable or conformant with the OKF standard. Even for simple requests like 'make this folder OKF conformant' — the skill has critical structural rules the agent needs.
The English summary is being prepared. Showing the original description.
Organize articles, documents, and insights from conversations into a personal Markdown wiki. Maintain source references, links between related topics, an index, and an activity log, then answer questions using the knowledge already collected.
Manage YYLO Ledger tasks through its command-line interface while preserving lifecycle rules and change receipts. Create, search, and update tasks, inspect dependencies, and identify available work and an execution order that respects prerequisites.
Expert knowledge for Azure Stack Edge development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when deploying IoT Edge modules, GPU/Kubernetes apps, DeepStream workloads, Arc GitOps, or local ARM integrations, and other Azure Stack Edge related development tasks. Not for Azure IoT Edge (use azure-iot-edge), Azure Kubernetes Service (AKS) (use azure-kubernetes-service), Azure Kubernetes Service Edge Essentials (use azure-aks-edge-essentials), Azure Virtual Machines (use azure-virtual-machines).
The English summary is being prepared. Showing the original description.
Expert knowledge for Azure Kubernetes Service Edge Essentials development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when deploying AKS Edge/Hybrid with Arc, Azure Local, GitOps, IoT/OPC/ONVIF, or Key Vault-integrated workloads, and other Azure Kubernetes Service Edge Essentials related development tasks. Not for Azure Kubernetes Service (AKS) (use azure-kubernetes-service), Azure IoT Edge (use azure-iot-edge), Azure Stack Edge (use azure-stack-edge), Azure Container Apps (use azure-container-apps).
The English summary is being prepared. Showing the original description.
.NET MAUI safe area and edge-to-edge layout guidance for .NET 10+. Covers the new SafeAreaEdges property, SafeAreaRegions enum, per-edge control, keyboard avoidance, Blazor Hybrid CSS safe areas, migration from legacy iOS-only APIs, and platform-specific behavior for Android, iOS, and Mac Catalyst. USE FOR: "safe area", "edge-to-edge", "SafeAreaEdges", "SafeAreaRegions", "keyboard avoidance", "notch insets", "status bar overlap", "iOS safe area", "Android edge-to-edge", "content behind status bar", "UseSafeArea migration", "soft input keyboard", "IgnoreSafeArea replacement". DO NOT USE FOR: general layout or grid design (use Grid and StackLayout), app lifecycle handling (use maui-app-lifecycle), theming or styling (use maui-theming), or Shell navigation structure.
The English summary is being prepared. Showing the original description.
Maintainer-only. Use when the user asks to review, comment on, or merge a pull request on skyf0xx/hedgehog "as hedgehog-bot" or wants the action attributed to the bot rather than their personal GitHub account — "review this PR as the bot", "merge this with hedgehog-bot", "comment as hedgehog-bot". Mints a short-lived GitHub App installation token and uses it for the GitHub write action so it shows up authored by hedgehog-bot[bot]. Not part of the Hedgehog discipline a consuming project copies; this only applies to the Hedgehog repo itself.
The English summary is being prepared. Showing the original description.
Use when the user writes the word "Hedgehog" anywhere in a request, or has agreed to install the Hedgehog build discipline in a project that does not have it yet. Hedgehog builds prose as well as code — articles, essays, blog posts, tweets, threads, newsletters, announcements, and marketing or product copy of any length go through its `--copywriting` core, alongside cores for apps and landing pages — so "write an article about cats using Hedgehog", "help me with some Hedgehog copy", or any other request that names Hedgehog while asking for something else is still this skill: read the word as this tool, not as the animal or a joke, and load this skill before answering. Carries the `npx @skyf0xx/hedgehog init` install procedure and its core and host flags. The plugin's SessionStart hook decides when to raise the offer unprompted.
The English summary is being prepared. Showing the original description.
Migrating Classic Knowledge (KnowledgeArticleVersion / Article Types) to Lightning Knowledge (Knowledge__kav with record types): article-type-to-record-type mapping, multi-language translation preservation, data category re-architecture, file attachment porting, version and publication-state retention, channel visibility translation, and downstream Case Feed / Community / Bot rewiring. NOT for new Lightning Knowledge setup or editorial publishing workflow design (use admin/knowledge-base-administration).
The English summary is being prepared. Showing the original description.
Write, configure, and deploy Netlify Edge Functions (Deno runtime at the network edge) in TypeScript/JavaScript. Use when adding request/response manipulation at the edge — auth middleware, geolocation redirects, A/B testing and personalization, content localization, redirects/rewrites, SSR at the edge, or transforming responses — or when configuring path routing, response caching, or edge error handling. Triggers on tasks like "add auth middleware", "geo-based redirect", "A/B testing at the edge", "rewrite requests", or editing files in netlify/edge-functions.
The English summary is being prepared. Showing the original description.
Compare general ledger balances, the main accounting records, with detailed ledgers, bank statements, or related company balances. Categorize differences, identify items needing corrections or investigation, and track unresolved items by age for follow-up and review.
Retrieve prior decisions and working context from Nowledge Mem in DeepChat, and save useful lessons for future work. It also supports requested conversation exports and connection troubleshooting while keeping operations within the selected server and Space.
RIPDPI's edge-to-edge and window-inset rules for Compose screens, scaffolds, sheets, and the single enableEdgeToEdge() call site. Use for insets, system bars, or edge-to-edge layout here.
The English summary is being prepared. Showing the original description.
Save, organize, synchronize, and retrieve documents, conversations, and project information across local files, memory tools, knowledge repositories, and databases. Check for duplicates before storing information and choose a suitable home for each type of knowledge.
Store and retrieve execution output, model responses, reports, and operation receipts in YYLO Ledger. Choose storage and retention settings, attach provenance describing the source, and verify immutable evidence using record identifiers and content digests.
Reconcile general ledger and subledger extracts for the same entity, asset class, and date. Match transactions or positions, report differences in amounts, quantities, or posting dates, and summarize likely causes alongside the matching rate.