Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

$pwd:

oneshotprompt-cli

Name: Oneshotprompt Cli
Author: jihadkhawaja

// Repository guidance for agents that need to communicate with the OneShotPrompt CLI, validate configs, list jobs, run specific jobs, or publish the console app.

In Manus ausführen

$ git log --oneline --stat

stars:0

forks:0

updated:5. April 2026 um 18:10

SKILL.md

readonly

name	oneshotprompt-cli
description	Repository guidance for agents that need to communicate with the OneShotPrompt CLI, validate configs, list jobs, run specific jobs, or publish the console app.
argument-hint	What OneShotPrompt CLI action, config path, or job should be operated on?
user-invocable	false
metadata	{"author":"oneshotprompt","version":"1.0"}

Use this skill when working inside the OneShotPrompt repository and the task involves the product CLI, scripts, docs, tests, or examples that exercise that CLI.

Primary commands:

dotnet restore OneShotPrompt.slnx
dotnet build OneShotPrompt.slnx
dotnet test tests/OneShotPrompt.Tests/OneShotPrompt.Tests.csproj
dotnet run --project src/OneShotPrompt.Console -- validate --config <path>
dotnet run --project src/OneShotPrompt.Console -- jobs --config <path>
dotnet run --project src/OneShotPrompt.Console -- run --config <path>
dotnet run --project src/OneShotPrompt.Console -- run --config <path> --job <name>
dotnet run --project src/OneShotPrompt.Console -- listen --config <path> --job <name>
dotnet run --project src/OneShotPrompt.Console -- interactive

Workflow:

Prefer explicit CLI commands over the no-argument launch path when writing automation, docs, tests, or examples.
Treat the config file directory as the runtime root for sibling skills/, logs/, and .oneshotprompt/memory/ content.
Validate a config before assuming a job can be listed or run.
List jobs before referencing a job name that was not already established.
When documenting or testing single-job execution, use run --config <path> --job <name>.
When documenting the WhatsApp personal channel flow, use listen --config <path> --job <name> if the intent is continuous event-driven replies rather than a single pass.
When describing interactive behavior, distinguish between explicit interactive and the no-argument behavior that depends on whether the terminal is interactive.
For build or test validation in this repo, use the solution and test commands above rather than ad hoc project combinations unless the task is intentionally scoped to one project.
If jobs or config examples mention execution behavior, account for both Workflow: "single-agent" and Workflow: "corporate-planning" where relevant.
If you change CLI behavior, command examples, scheduling flows, or bundled skills, update README.md and the relevant docs/ pages in the same change.

Guardrails:

Do not document or script unsupported subcommands or flags.
Do not treat --job as valid for validate or jobs.
Do not describe listen as a general scheduler; it is a targeted bridge-driven listener mode.
Do not describe logs or memory as repo-root relative unless the active config file is at the repo root.
Do not describe every run as a single execution agent when a job can opt into the corporate-planning workflow.
Do not rely on shell-specific syntax in examples unless the task is explicitly shell-specific.

related-skills.json

gleiches Repository

whatsapp-personal-channel.md

from "jihadkhawaja/OneShotPrompt"

Operate the local unofficial WhatsApp personal channel bridge for a personal account, limited to the allowlisted phone number or numbers in the bridge config.

2026-04-050

oneshotprompt-cli.md

from "jihadkhawaja/OneShotPrompt"

Operate the OneShotPrompt CLI predictably for validation, job discovery, targeted execution, and publishing. Use when a task is specifically about this project's command surface, config-driven runs, or the published console binary.

2026-04-050

file-system-mutations.md

from "jihadkhawaja/OneShotPrompt"

Plan and perform minimal local filesystem changes after inspection. Use when a task requires creating folders, moving or copying files, deleting files, or writing text files.

2026-03-080

professional-software-engineering.md

from "jihadkhawaja/OneShotPrompt"

Internal project-agent engineering workflow for implementing features and fixes with unit tests, clean abstractions, extensible design, repeatable setup, cross-platform execution, and Docker-ready delivery. Use when the agent is building, refactoring, hardening, testing, packaging, or operationalizing software professionally.

2026-03-070

command-execution.md

from "jihadkhawaja/OneShotPrompt"

Run installed executables directly for cross-platform automation. Use when a task needs CLI-based work, scripted workflows, repository commands, or tool-driven operations that are broader than simple file reads and writes.

2026-03-070

file-system-inspector.md

from "jihadkhawaja/OneShotPrompt"

Inspect and understand local files and directories before planning or making changes. Use when a task mentions files, folders, paths, Downloads, Documents, Desktop, reading text files, or checking current filesystem state.

2026-03-070

package.json

"author": "jihadkhawaja"

"repository": "jihadkhawaja/OneShotPrompt"

GitHub-Repository öffnen Creator-Repositorys ansehen

$ install --global

$ download --local

In Manus ausführen

$ useful --forSOC

SoftwareentwicklerInformatik- und Mathematikberufe15-1252L4

name	oneshotprompt-cli
description	Repository guidance for agents that need to communicate with the OneShotPrompt CLI, validate configs, list jobs, run specific jobs, or publish the console app.
argument-hint	What OneShotPrompt CLI action, config path, or job should be operated on?
user-invocable	false
metadata	{"author":"oneshotprompt","version":"1.0"}

Use this skill when working inside the OneShotPrompt repository and the task involves the product CLI, scripts, docs, tests, or examples that exercise that CLI.

Primary commands:

dotnet restore OneShotPrompt.slnx
dotnet build OneShotPrompt.slnx
dotnet test tests/OneShotPrompt.Tests/OneShotPrompt.Tests.csproj
dotnet run --project src/OneShotPrompt.Console -- validate --config <path>
dotnet run --project src/OneShotPrompt.Console -- jobs --config <path>
dotnet run --project src/OneShotPrompt.Console -- run --config <path>
dotnet run --project src/OneShotPrompt.Console -- run --config <path> --job <name>
dotnet run --project src/OneShotPrompt.Console -- listen --config <path> --job <name>
dotnet run --project src/OneShotPrompt.Console -- interactive

Workflow:

Prefer explicit CLI commands over the no-argument launch path when writing automation, docs, tests, or examples.
Treat the config file directory as the runtime root for sibling skills/, logs/, and .oneshotprompt/memory/ content.
Validate a config before assuming a job can be listed or run.
List jobs before referencing a job name that was not already established.
When documenting or testing single-job execution, use run --config <path> --job <name>.
When documenting the WhatsApp personal channel flow, use listen --config <path> --job <name> if the intent is continuous event-driven replies rather than a single pass.
When describing interactive behavior, distinguish between explicit interactive and the no-argument behavior that depends on whether the terminal is interactive.
For build or test validation in this repo, use the solution and test commands above rather than ad hoc project combinations unless the task is intentionally scoped to one project.
If jobs or config examples mention execution behavior, account for both Workflow: "single-agent" and Workflow: "corporate-planning" where relevant.
If you change CLI behavior, command examples, scheduling flows, or bundled skills, update README.md and the relevant docs/ pages in the same change.

Guardrails:

Do not document or script unsupported subcommands or flags.
Do not treat --job as valid for validate or jobs.
Do not describe listen as a general scheduler; it is a targeted bridge-driven listener mode.
Do not describe logs or memory as repo-root relative unless the active config file is at the repo root.
Do not describe every run as a single execution agent when a job can opt into the corporate-planning workflow.
Do not rely on shell-specific syntax in examples unless the task is explicitly shell-specific.

oneshotprompt-cli

Mehr aus diesem Repository

Mehr aus diesem Repository