Run any Skill in Manus with one click

code-notify

Stars14

Forks1

UpdatedMarch 16, 2026 at 17:10

Use when a task should trigger a local completion notification through code-notify, or when configuring cross-tool notification behavior for Codex, Cursor, Claude, Gemini, or similar agent workflows. Verify the installed command or existing local integration before relying on it.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

saski

saski/augmentedcode-configuration

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	code-notify
description	Use when a task should trigger a local completion notification through code-notify, or when configuring cross-tool notification behavior for Codex, Cursor, Claude, Gemini, or similar agent workflows. Verify the installed command or existing local integration before relying on it.

Code Notify

Goal

Make supported AI tools finish noisy terminal work with a local notification instead of requiring manual polling.

Use This Skill When

The user asks to enable or wire completion notifications for an AI coding tool.
A workflow should notify when a long-running task finishes or needs attention.
You are documenting shared agent capabilities in a cross-tool setup.

Cross-Platform Rules

Treat code-notify as an optional local dependency managed outside this repository.
Verify the installed command, wrapper, hook, or config before using it.
Prefer shared wording and forward-slash paths so the guidance works across macOS, Linux, and Windows-compatible shells.
Keep the integration additive. Do not replace existing hooks or notification settings unless the user asks.

Workflow

Detect whether the current tool already has a notification hook or wrapper configured.
Look for a local code-notify command, alias, script, or documented install path before assuming invocation details.
If present, use it for end-of-task or attention-needed notifications only.
If missing, tell the user the integration is unavailable in the current shell and continue without blocking the main task.

Output Guidance

Mention that code-notify is available only after verifying the local installation.
Keep notification instructions tool-agnostic unless the user asks for a specific platform.
Prefer concise setup notes over tool-specific prose duplication.

More from this repository

same repository

personal-knowledge-routing

saski/augmentedcode-configuration

Route durable personal context and reusable knowledge between augmentedcode-configuration and the personal knowledge vault. Use when the user asks to remember, persist, capture, retrieve, or organize personal knowledge; when deciding whether information belongs in rules, skills, portfolio, notes, maps, or inbox; or when using personal-knowledge-vault as a low-context reference layer.

2026-06-1714

github-host-alias

saski/augmentedcode-configuration

Use when running git clone, git remote add, git remote set-url, or suggesting GitHub SSH commands to ensure all GitHub access uses the saski SSH host alias.

2026-06-1714

building-data-apps

saski/augmentedcode-configuration

Build modern data apps, dashboards, and interactive reports using either React + Vite or Streamlit. Includes optional Gemini Data Analytics chat integration for an AI powered "chat with your data" experience. Relevant when any of the following conditions are true: 1. User explicitly requests to build a data dashboard, data application, or visualization UI, and the UI pulls data from a GCP database (defaulting to BigQuery unless otherwise specified). 2. You need to generate a frontend web application to interact with, query, and visualize data from GCP data sources. 3. User wants to build a "chat with your data" experience or integrate the Gemini Data Analytics chat API into a web interface. Do NOT use when any of the following conditions are true: 1. The request is for building backend-only services. 2. The request is for simple CLI scripts or command-line applications. 3. The web application is not data-centric or does not involve visualizing/querying data from GCP sources.

2026-06-0314

gcp-spark

saski/augmentedcode-configuration

Develops and executes Spark code on Dataproc Clusters and Serverless. Reads and writes data using BigLake Iceberg catalogs, BigQuery and Spanner. Debugs execution failures. Use when: - Writing Spark ETL pipelines on GCP. - Training or running inference with ML models with spark on GCP. - Managing Spark clusters, jobs, batches, and interactive sessions. Don't use when: - Writing generic Python scripts that don't use Spark. - Performing simple SQL queries that can be done directly in BigQuery.

2026-06-0314

lustra

saski/augmentedcode-configuration

Use when the user wants to clean up AI slop, harden a codebase, or run technical due diligence: review code for security flaws and vulnerable or wrongly-licensed dependencies, find and remove dead code, audit dependency health, run and triage linters, type checkers, test suites and formatters, evaluate design principles (SOLID and the cohesion/coupling equivalents for non-OO stacks), audit logging and observability, find performance smells, check documentation and CI health, scaffold baseline configs for the detected stack, do a structured code review, guide a one-major-at-a-time dependency migration, fix project structure, or produce one aggregated health report across all of these. Triggers on phrases like clean this up, find security issues, remove dead code, check dependencies, lint, typecheck, run the tests, format, review my code, check the design, check logging, is this slow, migrate a dependency, fix the project structure, set up the project, audit everything, due diligence, or this looks like AI slop

2026-06-0314

llm-council

saski/augmentedcode-configuration

Run any question, idea, or decision through a council of 5 AI advisors who independently analyze it, peer-review each other anonymously, and synthesize a final verdict. Based on Karpathy's LLM Council methodology. MANDATORY TRIGGERS: 'council this', 'run the council', 'war room this', 'pressure-test this', 'stress-test this', 'debate this'. STRONG TRIGGERS (use when combined with a real decision or tradeoff): 'should I X or Y', 'which option', 'what would you do', 'is this the right move', 'validate this', 'get multiple perspectives', 'I can't decide', 'I'm torn between'. Do NOT trigger on simple yes/no questions, factual lookups, or casual 'should I' without a meaningful tradeoff (e.g. 'should I use markdown' is not a council question). DO trigger when the user presents a genuine decision with stakes, multiple options, and context that suggests they want it pressure-tested from multiple angles.

2026-05-2714

name	code-notify
description	Use when a task should trigger a local completion notification through code-notify, or when configuring cross-tool notification behavior for Codex, Cursor, Claude, Gemini, or similar agent workflows. Verify the installed command or existing local integration before relying on it.

Code Notify

Goal

Make supported AI tools finish noisy terminal work with a local notification instead of requiring manual polling.

Use This Skill When

The user asks to enable or wire completion notifications for an AI coding tool.
A workflow should notify when a long-running task finishes or needs attention.
You are documenting shared agent capabilities in a cross-tool setup.

Cross-Platform Rules

Treat code-notify as an optional local dependency managed outside this repository.
Verify the installed command, wrapper, hook, or config before using it.
Prefer shared wording and forward-slash paths so the guidance works across macOS, Linux, and Windows-compatible shells.
Keep the integration additive. Do not replace existing hooks or notification settings unless the user asks.

Workflow

Detect whether the current tool already has a notification hook or wrapper configured.
Look for a local code-notify command, alias, script, or documented install path before assuming invocation details.
If present, use it for end-of-task or attention-needed notifications only.
If missing, tell the user the integration is unavailable in the current shell and continue without blocking the main task.

Output Guidance

Mention that code-notify is available only after verifying the local installation.
Keep notification instructions tool-agnostic unless the user asks for a specific platform.
Prefer concise setup notes over tool-specific prose duplication.