Yusuf Akçakaya avatar

Yusuf Akçakaya

Community

@fusuyfusuy · Istanbul, TR

14Followers
|
42Public Repos
|
11Published Skills

Yusuf Akçakaya publishes agent-governance skills for multi-agent coordination, AST code intelligence, architectural review, and technical-debt tracking.

Skills Distribution
DomainDeveloper To...Agent Orchestratio.. (35%)Code Intelligence .. (25%)Architecture Revie.. (25%)Technical Debt & S.. (15%)

Agent Skills by Yusuf Akçakaya

Showing 11 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About Yusuf Akçakaya

FAQPage Schema
What tasks can I accomplish with Yusuf Akçakaya's skills?▼

You can orchestrate multi-agent swarms, run AST-based symbol search and blast-radius analysis, conduct boundary-first code reviews with scoring calibration, interrogate architecture before coding, select engineering personas like Ousterhout or Lamport, summarize sessions, and harvest ponytail debt comments into a ledger.

Who are these skills designed for?▼

Software engineers and technical leads managing agent-assisted development. They suit operators coordinating autonomous subagents, architects needing adversarial design interrogation, and developers wanting smoke-first TDD, minimal-diff iteration, and tracked technical debt across repositories.

How do I install and run these skills in a project?▼

Use the add-skills skill to opt a repository into suites from the shared library (interfaces, matt, specterops), or add-mcp-server to enable MCP servers (ast, browser, context7, context, akatsuki). Mimori and akatsuki run via native CLI and MCP stdio.

Are these skills tied to a specific model or harness?▼

No. Boundary-review is explicitly harness- and model-agnostic, operating via parallel subagents or sequential passes across any agent environment. Most skills set disable-model-invocation, meaning they trigger only on explicit user request rather than automatic model invocation.

What prerequisites or dependencies do these skills require?▼

Skills draw from a shared library of suites and MCP servers, enabled per-project through add-skills and add-mcp-server. Akatsuki requires access to the operator's Phoenix second brain for architecture orientation and work-log deposits; mimori needs no configuration for AST indexing.