gravity

Scan documentation and logs to identify recurring manual tasks for formalization.

46|5|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/victoriacity/openakari --skill gravity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gravity
Source: https://github.com/victoriacity/openakari/tree/main/.claude/skills/gravity
Command: npx skills add https://github.com/victoriacity/openakari --skill gravity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify and formalize recurring manual tasks or workarounds into more robust infrastructure, reducing repetitive effort and improving system consistency.

Core Features & Use Cases

  • Pattern Detection: Scans documentation and logs for recurring manual steps or workarounds.
  • Formalization Evaluation: Assesses the recurrence, stability, and cost-benefit of migrating patterns to skills, conventions, or code.
  • Use Case: If agents repeatedly perform the same manual data validation steps across multiple sessions, this skill can evaluate whether to create a new automated script or a standardized convention to handle it.

Quick Start

Use the gravity skill to scan for recurring patterns across the repository.

Frequently Asked Questions about gravity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify recurring manual tasks in my workflow for automation?

Identify recurring manual tasks by scanning documentation and logs to detect repeated workarounds or manual steps. This pattern detection evaluates recurrence and stability to determine if workflow optimization through formalization is viable.

What is the best way to formalize repeated agent workflows into infrastructure?

Formalize repeated agent workflows by evaluating the cost-benefit of migrating stable, recurring judgments into standardized infrastructure. This process converts manual procedures into reusable skills, conventions, or code for systematic improvement.

When should I migrate manual workarounds to code or conventions?

Migrate manual workarounds to code or conventions when pattern detection confirms their recurrence and stability across sessions. A cost-benefit evaluation assesses whether formalizing these repeated procedures reduces repetitive effort and improves consistency.

How do I evaluate if a recurring workaround should become an automated script?

Evaluate a recurring workaround for automation by scanning logs to assess its frequency and stability. If the pattern detection confirms repeated manual validation steps across sessions, formalizing it into a script or convention improves consistency.

Can I scan repository logs to find patterns for workflow optimization?

You can scan repository documentation and logs to find recurring manual patterns. This pattern detection identifies repeated workarounds and evaluates their suitability for formalization into automated infrastructure, skills, or standardized conventions.

What are the limitations of formalizing manual tasks into infrastructure?

Formalization of manual tasks requires stable and recurring patterns to be effective. If workarounds are infrequent or unstable, migrating them to code or conventions may not yield sufficient cost-benefit to justify the infrastructure overhead.