Total 58,171 skills
Showing 12 of 58171 skills
Configure Celigo lookup cache resources -- in-memory key-value stores used for fast lookups, deduplication, cross-reference resolution, and state tracking during flow execution. Use when creating caches, loading data, referencing caches in import lookups, or managing cache lifecycle.
Manage Celigo account users -- inviting users, updating permissions, configuring access levels (administrator, manage, monitor, integration-only), enforcing MFA/SSO, and disabling accounts. Use when adding team members, changing permissions, auditing access, or managing user lifecycle.
Diagnose and resolve Celigo flow failures -- total failures, partial errors, stuck jobs, empty runs, and performance issues. Use when a flow is failing, producing errors, returning no data, or running slowly.
Manage Celigo integrations -- the named containers that group flows, APIs, Tools, connections, scripts, and settings so a body of automation is organized, secured, and evolved as one unit. Covers plain integrations vs Integration Apps, parent/child hierarchies, cloning with connection remap, moving resources between integrations, notifications, aliases, and Integration Lifecycle Management (ILM) revisions/snapshots/pulls/reverts across environments. Use when creating, organizing, cloning, promoting, or versioning integrations, or deciding whether new work belongs in an existing integration or its own.
Build Celigo MCP server resources -- endpoints that expose Tools and builder-mode APIs to external AI agents and MCP clients. Use when creating MCP servers, linking tools or APIs, or configuring annotations and overrides.
A skill for reading, researching, and editing pages on Cosense (formerly Scrapbox). Used when users make requests like "Look up XX on Cosense", "Read this Cosense page", "Do XX on Scrapbox", "View the page on scrapbox.io", "Add a comment to this page", etc. Retrieves pages using the cosense CLI and answers users' questions while citing the source of information.
Activate this skill when users are in the early weak stage and need to plan a 0-to-1 expansion path. Typical trigger signals: Limited resources but great ambition, facing the choice between "full-scale rollout or focused breakthrough", and the team showing a "roving bandit" tendency (chasing trends without deep cultivation). Scenarios where this skill is not called: Having a solid base and only needing optimization, limited market scale that does not require expansion, problems lying in execution rather than strategic paths. Difference from the "Asymmetric Strategy" skill: This skill solves "where to fight and how to expand" (path layer), while the latter solves "what paradigm to use for competition" (strategy layer).
Activated when users need to plan long-term competitive strategies against significantly stronger opponents (giant entry, resource gaps, brand disadvantages). Typical trigger signals: "Big companies are entering our track too", "Their resources are 100 times ours", "What should we do if we can't beat them?" Non-activation scenarios: Competitive situations where both sides are evenly matched or you have the upper hand, short-term solvable challenges, non-competitive decisions. Difference from "Concentrate Superior Forces": This skill plans the overall timeline and phased strategies, while the latter plans resource allocation for specific campaigns.
This skill is activated when users are faced with multiple intertwined problems, unable to determine priorities, and trapped in decision paralysis where "everything seems important". Typical trigger signals: Stagnant company growth with multiple departments reporting issues simultaneously, limited resources but unlimited demands, and teams arguing endlessly about direction without focus. Scenarios where it should not be invoked: The problem is clear and single, only execution is needed rather than analysis, or the user requires tool operations rather than strategic judgment. Difference from the "Concentrate Superior Forces" skill: This skill solves the problem of "seeing the full picture of the issue and identifying bottlenecks", while the latter solves "how to concentrate resources to break through after clarifying the situation".
This skill is activated when the user's team faces execution problems—such as failing to meet OKRs, constantly changing plans, and passive team response to instructions. Typical trigger signals: Goals are set but execution deviates, plans can't keep up with changes, and the team only completes assigned tasks without proactive thinking. Non-trigger scenarios: Execution is good and only needs fine-tuning, the problem lies at the strategic level rather than the execution level, and individual work does not require a team execution framework. Difference from the "Strategy-Tactics Dialectics" skill: This skill solves "how to balance the three dimensions of execution" (execution layer), while the latter solves "dialectical design of offensive and defensive levels" (strategy layer).
Restructure a segment of unintegrated local Git fragmented history into a small number of clear commits grouped by actual file content. This is used when the user calls $my-curate-git-history, or explicitly requests to recommit, rewrite, or squash a segment of local commit history; by default, it uses upstream/main as the baseline, targets approximately 20% of the original number of commits, and retains recoverable references and the actual timestamps from the original commits. Do not use this when only analysis, regular commits, or organizing integrated history is requested.
This skill is activated when users need to choose their own action rhythm based on the status of competitors. Typical trigger signals: Unsure whether to attack or defend against a strong competitor, being led by the competitor's rhythm, always one step behind in passive response. Scenarios where it is not called: Blue ocean markets with no clear competitors, stable competitive situations that do not require rhythm adjustments, users need strategic planning rather than action rhythm. Difference from the "Asymmetric Strategy" skill: This skill solves the problem of "whether to attack or defend at this moment" (rhythm level), while the latter solves the problem of "what paradigm to use for competition" (strategic level).