Automates long-duration tasks using a predefined Task Contract with OUTCOME, EXCLUSIONS, DURATION and GUARDRAILS.
npx skills add https://github.com/ioku24/autorankr --skill autonomous
Please help me install this Agent Skill. Skill: autonomous Source: https://github.com/ioku24/autorankr/tree/main/.claude/skills/autonomous Command: npx skills add https://github.com/ioku24/autorankr --skill autonomous
This Skill enables teams and AI systems to tackle long-duration tasks (1-2+ hours) without continuous supervision after an initial clarification, dramatically reducing manual oversight and handoffs.
To begin, provide a Task Contract with the fields OUTCOME, EXCLUSIONS, DURATION, and GUARDRAILS. Then indicate readiness (e.g., respond with "go" or "start") to commence autonomous execution.
Example Task Contract: OUTCOME: [What success looks like - measurable] EXCLUSIONS: [What I will NOT do] DURATION: [Time limit, e.g., "2 hours"] GUARDRAILS: [Hard limits - code/logic to never touch]
High-intent search queries and answers about installing and using this skill.
You can automate long-duration tasks by defining a Task Contract with specific OUTCOME, EXCLUSIONS, DURATION, and GUARDRAILS. Once provided, the system executes the work autonomously through structured phases including clarification, planning, execution, and reporting.
A Task Contract is a structured input that bounds autonomous execution by specifying the desired OUTCOME, EXCLUSIONS, DURATION, and GUARDRAILS. It ensures safe, structured work on complex projects by enforcing hard limits and clear success metrics before execution begins.
Yes, autonomous execution is suitable for complex research, writing, and data analysis projects. It channels sustained work through a phase-based execution plan, allowing AI agents to tackle cross-domain projects that require long periods of focused, structured work.
The primary limitation is that autonomous execution requires a fully predefined Task Contract upfront. Without clear OUTCOME, EXCLUSIONS, DURATION, and GUARDRAILS, the system cannot safely bound operations, making it unsuitable for open-ended tasks lacking measurable success criteria.
To start autonomous task execution, provide the Task Contract fields and then indicate readiness by responding with a trigger word like "go" or "start". The system will then transition from the clarification phase into the execution plan and autonomous work phases.
No, autonomous task execution is designed for long-duration tasks lasting one to two hours or more. It is built for sustained, structured work rather than short, quick queries, significantly reducing manual oversight and handoffs for complex projects.
ruifrvazInitiate work on a specified task and set the workflow mode.
Tubular-HealthExecute one sub-task from a refined issue and stop after completion.
ilanf23Define design team workflows for task management, communication, and tooling integration.
chainkemistsStandardize multi-session software development workflows with phase-gate and documentation protocols.
