[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75BN0G78J66AP0R075FSM0A":3,"skill-same:01M75BN0G78J66AP0R075FSM0A":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M75BN0G78J66AP0R075FSM0A","android-clean-architecture",null,"Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fandroid-clean-architecture\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: android-clean-architecture\ndescription: Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns.\norigin: ECC\n---\n\n# Android Clean Architecture\n\nClean Architecture patterns for Android and KMP projects. Covers module boundaries, dependency inversion, UseCase\u002FRepository patterns, and data layer design with Room, SQLDelight, and Ktor.\n\n## When to Activate\n\n- Structuring Android or KMP project modules\n- Implementing UseCases, Repositories, or DataSources\n- Designing data flow between layers (domain, data, presentation)\n- Setting up dependency injection with Koin or Hilt\n- Working with Room, SQLDelight, or Ktor in a layered architecture\n\n## Module Structure\n\n### Recommended Layout\n\n```\nproject\u002F\n├── app\u002F                  # Android entry point, DI wiring, Application class\n├── core\u002F                 # Shared utilities, base classes, error types\n├── domain\u002F               # UseCases, domain models, repository interfaces (pure Kotlin)\n├── data\u002F                 # Repository implementations, DataSources, DB, network\n├── presentation\u002F         # Screens, ViewModels, UI models, navigation\n├── design-system\u002F        # Reusable Compose components, theme, typography\n└── feature\u002F              # Feature modules (optional, for larger projects)\n    ├── auth\u002F\n    ├── settings\u002F\n    └── profile\u002F\n```\n\n### Dependency Rules\n\n```\napp → presentation, domain, data, core\npresentation → domain, design-system, core\ndata → domain, core\ndomain → core (or no dependencies)\ncore → (nothing)\n```\n\n**Critical**: `domain` must NEVER depend on `data`, `presentation`, or any framework. It contains pure Kotlin only.\n\n## Domain Layer\n\n### UseCase Pattern\n\nEach UseCase represents one business operation. Use `operator fun invoke` for clean call sites:\n\n```kotlin\nclass GetItemsByCategoryUseCase(\n    private val repository: ItemRepository\n) {\n    suspend operator fun invoke(category: String): Result\u003CList\u003CItem>> {\n        return repository.getItemsByCategory(category)\n    }\n}\n\n\u002F\u002F Flow-based UseCase for reactive streams\nclass ObserveUserProgressUseCase(\n    private val repository: UserRepository\n) {\n    operator fun invoke(userId: String): Flow\u003CUserProgress> {\n        return repository.observeProgress(userId)\n    }\n}\n```\n\n### Domain Models\n\nDomain models are plain Kotlin data classes — no framework annotations:\n\n```kotlin\ndata class Item(\n    val id: String,\n    val title: String,\n    val description: String,\n    val tags: List\u003CString>,\n    val status: Status,\n    val category: String\n)\n\nenum class Status { DRAFT, ACTIVE, ARCHIVED }\n```\n\n### Repository Interfaces\n\nDefined in domain, implemented in data:\n\n```kotlin\ninterface ItemRepository {\n    suspend fun getItemsByCategory(category: String): Result\u003CList\u003CItem>>\n    suspend fun saveItem(item: Item): Result\u003CUnit>\n    fun observeItems(): Flow\u003CList\u003CItem>>\n}\n```\n\n## Data Layer\n\n### Repository Implementation\n\nCoordinates between local and remote data sources:\n\n```kotlin\nclass ItemRepositoryImpl(\n    private val localDataSource: ItemLocalDataSource,\n    private val remoteDataSource: ItemRemoteDataSource\n) : ItemRepository {\n\n    override suspend fun getItemsByCategory(category: String): Result\u003CList\u003CItem>> {\n        return runCatching {\n            val remote = remoteDataSource.fetchItems(category)\n            localDataSource.insertItems(remote.map { it.toEntity() })\n            localDataSource.getItemsByCategory(category).map { it.toDomain() }\n        }\n    }\n\n    override suspend fun saveItem(item: Item): Result\u003CUnit> {\n        return runCatching {\n            localDataSource.insertItems(listOf(item.toEntity()))\n        }\n    }\n\n    override fun observeItems(): Flow\u003CList\u003CItem>> {\n        return localDataSource.observeAll().map { entities ->\n            entities.map { it.toDomain() }\n        }\n    }\n}\n```\n\n### Mapper Pattern\n\nKeep mappers as extension functions near the data models:\n\n```kotlin\n\u002F\u002F In data layer\nfun ItemEntity.toDomain() = Item(\n    id = id,\n    title = title,\n    description = description,\n    tags = tags.split(\"|\"),\n    status = Status.valueOf(status),\n    category = category\n)\n\nfun ItemDto.toEntity() = ItemEntity(\n    id = id,\n    title = title,\n    description = description,\n    tags = tags.joinToString(\"|\"),\n    status = status,\n    category = category\n)\n```\n\n### Room Database (Android)\n\n```kotlin\n@Entity(tableName = \"items\")\ndata class ItemEntity(\n    @PrimaryKey val id: String,\n    val title: String,\n    val description: String,\n    val tags: String,\n    val status: String,\n    val category: String\n)\n\n@Dao\ninterface ItemDao {\n    @Query(\"SELECT * FROM items WHERE category = :category\")\n    suspend fun getByCategory(category: String): List\u003CItemEntity>\n\n    @Upsert\n    suspend fun upsert(items: List\u003CItemEntity>)\n\n    @Query(\"SELECT * FROM items\")\n    fun observeAll(): Flow\u003CList\u003CItemEntity>>\n}\n```\n\n### SQLDelight (KMP)\n\n```sql\n-- Item.sq\nCREATE TABLE ItemEntity (\n    id TEXT NOT NULL PRIMARY KEY,\n    title TEXT NOT NULL,\n    description TEXT NOT NULL,\n    tags TEXT NOT NULL,\n    status TEXT NOT NULL,\n    category TEXT NOT NULL\n);\n\ngetByCategory:\nSELECT * FROM ItemEntity WHERE category = ?;\n\nupsert:\nINSERT OR REPLACE INTO ItemEntity (id, title, description, tags, status, category)\nVALUES (?, ?, ?, ?, ?, ?);\n\nobserveAll:\nSELECT * FROM ItemEntity;\n```\n\n### Ktor Network Client (KMP)\n\n```kotlin\nclass ItemRemoteDataSource(private val client: HttpClient) {\n\n    suspend fun fetchItems(category: String): List\u003CItemDto> {\n        return client.get(\"api\u002Fitems\") {\n            parameter(\"category\", category)\n        }.body()\n    }\n}\n\n\u002F\u002F HttpClient setup with content negotiation\nval httpClient = HttpClient {\n    install(ContentNegotiation) { json(Json { ignoreUnknownKeys = true }) }\n    install(Logging) { level = LogLevel.HEADERS }\n    defaultRequest { url(\"https:\u002F\u002Fapi.example.com\u002F\") }\n}\n```\n\n## Dependency Injection\n\n### Koin (KMP-friendly)\n\n```kotlin\n\u002F\u002F Domain module\nval domainModule = module {\n    factory { GetItemsByCategoryUseCase(get()) }\n    factory { ObserveUserProgressUseCase(get()) }\n}\n\n\u002F\u002F Data module\nval dataModule = module {\n    single\u003CItemRepository> { ItemRepositoryImpl(get(), get()) }\n    single { ItemLocalDataSource(get()) }\n    single { ItemRemoteDataSource(get()) }\n}\n\n\u002F\u002F Presentation module\nval presentationModule = module {\n    viewModelOf(::ItemListViewModel)\n    viewModelOf(::DashboardViewModel)\n}\n```\n\n### Hilt (Android-only)\n\n```kotlin\n@Module\n@InstallIn(SingletonComponent::class)\nabstract class RepositoryModule {\n    @Binds\n    abstract fun bindItemRepository(impl: ItemRepositoryImpl): ItemRepository\n}\n\n@HiltViewModel\nclass ItemListViewModel @Inject constructor(\n    private val getItems: GetItemsByCategoryUseCase\n) : ViewModel()\n```\n\n## Error Handling\n\n### Result\u002FTry Pattern\n\nUse `Result\u003CT>` or a custom sealed type for error propagation:\n\n```kotlin\nsealed interface Try\u003Cout T> {\n    data class Success\u003CT>(val value: T) : Try\u003CT>\n    data class Failure(val error: AppError) : Try\u003CNothing>\n}\n\nsealed interface AppError {\n    data class Network(val message: String) : AppError\n    data class Database(val message: String) : AppError\n    data object Unauthorized : AppError\n}\n\n\u002F\u002F In ViewModel — map to UI state\nviewModelScope.launch {\n    when (val result = getItems(category)) {\n        is Try.Success -> _state.update { it.copy(items = result.value, isLoading = false) }\n        is Try.Failure -> _state.update { it.copy(error = result.error.toMessage(), isLoading = false) }\n    }\n}\n```\n\n## Convention Plugins (Gradle)\n\nFor KMP projects, use convention plugins to reduce build file duplication:\n\n```kotlin\n\u002F\u002F build-logic\u002Fsrc\u002Fmain\u002Fkotlin\u002Fkmp-library.gradle.kts\nplugins {\n    id(\"org.jetbrains.kotlin.multiplatform\")\n}\n\nkotlin {\n    androidTarget()\n    iosX64(); iosArm64(); iosSimulatorArm64()\n    sourceSets {\n        commonMain.dependencies { \u002F* shared deps *\u002F }\n        commonTest.dependencies { implementation(kotlin(\"test\")) }\n    }\n}\n```\n\nApply in modules:\n\n```kotlin\n\u002F\u002F domain\u002Fbuild.gradle.kts\nplugins { id(\"kmp-library\") }\n```\n\n## Anti-Patterns to Avoid\n\n- Importing Android framework classes in `domain` — keep it pure Kotlin\n- Exposing database entities or DTOs to the UI layer — always map to domain models\n- Putting business logic in ViewModels — extract to UseCases\n- Using `GlobalScope` or unstructured coroutines — use `viewModelScope` or structured concurrency\n- Fat repository implementations — split into focused DataSources\n- Circular module dependencies — if A depends on B, B must not depend on A\n\n## References\n\nSee skill: `compose-multiplatform-patterns` for UI patterns.\nSee skill: `kotlin-coroutines-flows` for async patterns.\n","# Android Clean Architecture\n\nClean Architecture patterns for Android and KMP projects. Covers module boundaries, dependency inversion, UseCase\u002FRepository patterns, and data layer design with Room, SQLDelight, and Ktor.\n\n## When to Activate\n\n- Structuring Android or KMP project modules\n- Implementing UseCases, Repositories, or DataSources\n- Designing data flow between layers (domain, data, presentation)\n- Setting up dependency injection with Koin or Hilt\n- Working with Room, SQLDelight, or Ktor in a layered architecture\n\n## Module Structure\n\n### Recommended Layout\n\n```\nproject\u002F\n├── app\u002F                  # Android entry point, DI wiring, Application class\n├── core\u002F                 # Shared utilities, base classes, error types\n├── domain\u002F               # UseCases, domain models, repository interfaces (pure Kotlin)\n├── data\u002F                 # Repository implementations, DataSources, DB, network\n├── presentation\u002F         # Screens, ViewModels, UI models, navigation\n├── design-system\u002F        # Reusable Compose components, theme, typography\n└── feature\u002F              # Feature modules (optional, for larger projects)\n    ├── auth\u002F\n    ├── settings\u002F\n    └── profile\u002F\n```\n\n### Dependency Rules\n\n```\napp → presentation, domain, data, core\npresentation → domain, design-system, core\ndata → domain, core\ndomain → core (or no dependencies)\ncore → (nothing)\n```\n\n**Critical**: `domain` must NEVER depend on `data`, `presentation`, or any framework. It contains pure Kotlin only.\n\n## Domain Layer\n\n### UseCase Pattern\n\nEach UseCase represents one business operation. Use `operator fun invoke` for clean call sites:\n\n```kotlin\nclass GetItemsByCategoryUseCase(\n    private val repository: ItemRepository\n) {\n    suspend operator fun invoke(category: String): Result\u003CList\u003CItem>> {\n        return repository.getItemsByCategory(category)\n    }\n}\n\n\u002F\u002F Flow-based UseCase for reactive streams\nclass ObserveUserProgressUseCase(\n    private val repository: UserRepository\n) {\n    operator fun invoke(userId: String): Flow\u003CUserProgress> {\n        return repository.observeProgress(userId)\n    }\n}\n```\n\n### Domain Models\n\nDomain models are plain Kotlin data classes — no framework annotations:\n\n```kotlin\ndata class Item(\n    val id: String,\n    val title: String,\n    val description: String,\n    val tags: List\u003CString>,\n    val status: Status,\n    val category: String\n)\n\nenum class Status { DRAFT, ACTIVE, ARCHIVED }\n```\n\n### Repository Interfaces\n\nDefined in domain, implemented in data:\n\n```kotlin\ninterface ItemRepository {\n    suspend fun getItemsByCategory(category: String): Result\u003CList\u003CItem>>\n    suspend fun saveItem(item: Item): Result\u003CUnit>\n    fun observeItems(): Flow\u003CList\u003CItem>>\n}\n```\n\n## Data Layer\n\n### Repository Implementation\n\nCoordinates between local and remote data sources:\n\n```kotlin\nclass ItemRepositoryImpl(\n    private val localDataSource: ItemLocalDataSource,\n    private val remoteDataSource: ItemRemoteDataSource\n) : ItemRepository {\n\n    override suspend fun getItemsByCategory(category: String): Result\u003CList\u003CItem>> {\n        return runCatching {\n            val remote = remoteDataSource.fetchItems(category)\n            localDataSource.insertItems(remote.map { it.toEntity() })\n            localDataSource.getItemsByCategory(category).map { it.toDomain() }\n        }\n    }\n\n    override suspend fun saveItem(item: Item): Result\u003CUnit> {\n        return runCatching {\n            localDataSource.insertItems(listOf(item.toEntity()))\n        }\n    }\n\n    override fun observeItems(): Flow\u003CList\u003CItem>> {\n        return localDataSource.observeAll().map { entities ->\n            entities.map { it.toDomain() }\n        }\n    }\n}\n```\n\n### Mapper Pattern\n\nKeep mappers as extension functions near the data models:\n\n```kotlin\n\u002F\u002F In data layer\nfun ItemEntity.toDomain() = Item(\n    id = id,\n    title = title,\n    description = description,\n    tags = tags.split(\"|\"),\n    status = Status.valueOf(status),\n    category = category\n)\n\nfun ItemDto.toEntity() = ItemEntity(\n    id = id,\n    title = title,\n    description = description,\n    tags = tags.joinToString(\"|\"),\n    status = status,\n    category = category\n)\n```\n\n### Room Database (Android)\n\n```kotlin\n@Entity(tableName = \"items\")\ndata class ItemEntity(\n    @PrimaryKey val id: String,\n    val title: String,\n    val description: String,\n    val tags: String,\n    val status: String,\n    val category: String\n)\n\n@Dao\ninterface ItemDao {\n    @Query(\"SELECT * FROM items WHERE category = :category\")\n    suspend fun getByCategory(category: String): List\u003CItemEntity>\n\n    @Upsert\n    suspend fun upsert(items: List\u003CItemEntity>)\n\n    @Query(\"SELECT * FROM items\")\n    fun observeAll(): Flow\u003CList\u003CItemEntity>>\n}\n```\n\n### SQLDelight (KMP)\n\n```sql\n-- Item.sq\nCREATE TABLE ItemEntity (\n    id TEXT NOT NULL PRIMARY KEY,\n    title TEXT NOT NULL,\n    description TEXT NOT NULL,\n    tags TEXT NOT NULL,\n    status TEXT NOT NULL,\n    category TEXT NOT NULL\n);\n\ngetByCategory:\nSELECT * FROM ItemEntity WHERE category = ?;\n\nupsert:\nINSERT OR REPLACE INTO ItemEntity (id, title, description, tags, status, category)\nVALUES (?, ?, ?, ?, ?, ?);\n\nobserveAll:\nSELECT * FROM ItemEntity;\n```\n\n### Ktor Network Client (KMP)\n\n```kotlin\nclass ItemRemoteDataSource(private val client: HttpClient) {\n\n    suspend fun fetchItems(category: String): List\u003CItemDto> {\n        return client.get(\"api\u002Fitems\") {\n            parameter(\"category\", category)\n        }.body()\n    }\n}\n\n\u002F\u002F HttpClient setup with content negotiation\nval httpClient = HttpClient {\n    install(ContentNegotiation) { json(Json { ignoreUnknownKeys = true }) }\n    install(Logging) { level = LogLevel.HEADERS }\n    defaultRequest { url(\"https:\u002F\u002Fapi.example.com\u002F\") }\n}\n```\n\n## Dependency Injection\n\n### Koin (KMP-friendly)\n\n```kotlin\n\u002F\u002F Domain module\nval domainModule = module {\n    factory { GetItemsByCategoryUseCase(get()) }\n    factory { ObserveUserProgressUseCase(get()) }\n}\n\n\u002F\u002F Data module\nval dataModule = module {\n    single\u003CItemRepository> { ItemRepositoryImpl(get(), get()) }\n    single { ItemLocalDataSource(get()) }\n    single { ItemRemoteDataSource(get()) }\n}\n\n\u002F\u002F Presentation module\nval presentationModule = module {\n    viewModelOf(::ItemListViewModel)\n    viewModelOf(::DashboardViewModel)\n}\n```\n\n### Hilt (Android-only)\n\n```kotlin\n@Module\n@InstallIn(SingletonComponent::class)\nabstract class RepositoryModule {\n    @Binds\n    abstract fun bindItemRepository(impl: ItemRepositoryImpl): ItemRepository\n}\n\n@HiltViewModel\nclass ItemListViewModel @Inject constructor(\n    private val getItems: GetItemsByCategoryUseCase\n) : ViewModel()\n```\n\n## Error Handling\n\n### Result\u002FTry Pattern\n\nUse `Result\u003CT>` or a custom sealed type for error propagation:\n\n```kotlin\nsealed interface Try\u003Cout T> {\n    data class Success\u003CT>(val value: T) : Try\u003CT>\n    data class Failure(val error: AppError) : Try\u003CNothing>\n}\n\nsealed interface AppError {\n    data class Network(val message: String) : AppError\n    data class Database(val message: String) : AppError\n    data object Unauthorized : AppError\n}\n\n\u002F\u002F In ViewModel — map to UI state\nviewModelScope.launch {\n    when (val result = getItems(category)) {\n        is Try.Success -> _state.update { it.copy(items = result.value, isLoading = false) }\n        is Try.Failure -> _state.update { it.copy(error = result.error.toMessage(), isLoading = false) }\n    }\n}\n```\n\n## Convention Plugins (Gradle)\n\nFor KMP projects, use convention plugins to reduce build file duplication:\n\n```kotlin\n\u002F\u002F build-logic\u002Fsrc\u002Fmain\u002Fkotlin\u002Fkmp-library.gradle.kts\nplugins {\n    id(\"org.jetbrains.kotlin.multiplatform\")\n}\n\nkotlin {\n    androidTarget()\n    iosX64(); iosArm64(); iosSimulatorArm64()\n    sourceSets {\n        commonMain.dependencies { \u002F* shared deps *\u002F }\n        commonTest.dependencies { implementation(kotlin(\"test\")) }\n    }\n}\n```\n\nApply in modules:\n\n```kotlin\n\u002F\u002F domain\u002Fbuild.gradle.kts\nplugins { id(\"kmp-library\") }\n```\n\n## Anti-Patterns to Avoid\n\n- Importing Android framework classes in `domain` — keep it pure Kotlin\n- Exposing database entities or DTOs to the UI layer — always map to domain models\n- Putting business logic in ViewModels — extract to UseCases\n- Using `GlobalScope` or unstructured coroutines — use `viewModelScope` or structured concurrency\n- Fat repository implementations — split into focused DataSources\n- Circular module dependencies — if A depends on B, B must not depend on A\n\n## References\n\nSee skill: `compose-multiplatform-patterns` for UI patterns.\nSee skill: `kotlin-coroutines-flows` for async patterns.\n",{"name":5,"origin":23,"description":7},"ECC","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fandroid-clean-architecture",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add agisota\u002Fold-one --skill android-clean-architecture",{"tool":39,"command":40},"bunx","bunx skills add agisota\u002Fold-one --skill android-clean-architecture",{"tool":42,"command":43},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill android-clean-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fandroid-clean-architecture\u002FSKILL.md",true,[],[48,55,62,71,78,85],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":66,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]