open-index/open-npm huggingface dataset:
npm package: @talenguyen/andev
Description: A cli tools for Android developer
Author: Giang Nguyen
Latest version: 1.1.7

[![Build Status](https://travis-ci.org/talenguyen/andev.svg?branch=master)](https://travis-ci.org/talenguyen/andev)
[![npm](https://img.shields.io/badge/npm-v1.1.6-blue.svg)](https://www.npmjs.com/package/@talenguyen/andev)

# Andev

A cli tools for Android Developer

## Features

 * [x] Open deeplink 
 * [x] Clear cache
 * [x] Install apk
 * [x] Uninstall package
 * [x] Send text to device
 * [ ] Connect device over WI-FI

## Install

```shell
$ npm i -g @talenguyen/andev
```

## Usage

```shell
Usage:
    $ andev --help
    Options:
      --deeplink, d     Open deep-link
      --clear, c        Clear cache
      --uninstall, u    Uninstall 
      --install, i      Find and install APK in directory 
      --text, t         Send text to device
    Example:
      $ andev --d https://google.com
      $ andev --c com.android.chrome
      $ andev --uninstall com.android.chrome
      $ andev --install app/buid/output
      $ andev --text "Hello world"
```

## Author
- Giang Nguyen <giangnguyen.tale@gmail.com> ([twitter](https://twitter.com/Tale_Nguyen))

## License

[MIT](LICENSE)
npm package: @talenra/ngx-ui
Description: Reusable UI building blocks for talenra Angular apps.
Latest version: 0.1.3

# talenra UI-Component Library for Angular 

The talenra UI component library for Angular provides reusable building blocks for Angular apps. Using the pre-made components allows frontend developers to focus on the app-specific challenges. The library fuels rapid development of talenra apps that comply with the talenra design system.

> **IMPORTANT: This package is currently under development.**
>
> - Check for updates frequently.
> - [Join our developer chat](#resources) for news, announcements and support.
> - Expect breaking changes.
>
> We're here to help and happy to get feedback!

## Setup and Installation

The package `@talenra/ngx-ui` is served via the talenra artifactory. Access to the artifactory requires the TC user provided in the talenra onboarding process.

Add the `@talenra` registry to your npm configuration:

```sh
# Default registry
registry=https://registry.npmjs.com
```

Log in into the talenra registry using your TC account (username looks like `tcXXXXXX`):

```sh
npm login --scope=@talenra
```

And finally install the package.

```sh
npm i @talenra/ngx-ui
```

## Bug reports

Please [open a new issue](https://gitlab.svanet.ch/talenra-ui/talenra-ui-workspace/-/issues) to report
bugs. The better your report, the faster we can solve the issue. Information required to address the issue include:

- Environment (versions involved)
- Step-by-step guide on how to reproduce the bug
- Description of the current behaviour
- Description of the expected behaviour
- If the issue affects rendering, a screenshot might help

## Resources

- [Change log](./CHANGELOG.md)
- [Upgrade guide](./additional-documentation/upgrade.md)
- [Contribution guide](./CONTRIBUTING.md)
- [Code formatting and validation](./additional-documentation/code-formatting-and-validation.md)
- [Testing guide](./additional-documentation/testing.md)
- [Git hooks](./additional-documentation/git-hooks.md)
- [Git repository](https://gitlab.svanet.ch/talenra-ui/talenra-ui-workspace/): includes source code of
  the library and the demo app
- Developer chat channel (announcements and support): The channel is currently private. [Drop us a line](#contact) if
  you would like to join.
- CompLib-Lounge: Every other week we offer a developer hangout. Have a look at our [CompLib-Lounge Board](https://miro.com/app/board/uXjVO4b6mrs=/) and drop us a line to get invited. 

## Contact
npm package: @talensjr/react-scripts
Description: Configuration and scripts for Create React App.
Latest version: 1.1.2

# react-scripts

This package includes scripts and configuration used by [Create React App](https://github.com/facebookincubator/create-react-app).<br>
Please refer to its documentation:

* [Getting Started](https://github.com/facebookincubator/create-react-app/blob/master/README.md#getting-started) – How to create a new app.
* [User Guide](https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md) – How to develop apps bootstrapped with Create React App.
npm package: @talent-collective/ui
Description: ### Installation
Author: Talent Collective Admin
Latest version: 1.0.3

## A React UI library with Tailwind CSS, optimized for Next.js client and server components.

### Installation

For production:

```
yarn add @talent-collective/ui
```

For local testing use `yalc`(https://www.npmjs.com/package/yalc).

```
yarn global add yalc
```

### Local Development

Build: `yarn build`

Storybook: `yarn run storybook`

Local linking for development with yalc:

- Building package: `yarn build`
- Publish package locally: `yalc publish`
- Update package locally: `yalc publish --push`
- Building and updating package locally: `yarn run update`

### Consuming repository

- Update the tailwind.config `content` with

```
'./node_modules/@talent-collective/ui/**/*.{ts,tsx, js, tsx}',
'./.yalc/@talent-collective/ui/**/*.{ts,tsx,js, tsx}',
```

- Add to .gitignore the following:

```
.yalc
yalc.lock
```

- Link ui package in local dev: `yalc link @talent-collective/ui`
- Unlink package in local dev: `yalc remove @talent-collective/ui`

- Check for tree-shaking: `ANALYZE=true npm run build`

### Notes

1. The @types/next package provides type declarations for Next.js modules (next/link, next/image, etc.) without including the runtime code (because next is a peer dependency and isn’t available during type-checking/building the library).
2. List `next/link` or `next/image` and other modules if needed in the external arrays in `vite.config.js`.

### Publishing to npm

Publishing to public npm. It supports faster built and caching.

- Login to npm: `npm login` (2FA)
- Update the version
- Public updates: `npm publish --access=public`
npm package: @talent-scout/data-collector
Description: [![GitHub Actions](https://github.com/presence-io/talent-scout/actions/workflows/publish.yml/badge.svg)](https://github.com/presence-io/talent-scout/actions/workflows/publish.yml) [![npm: @talent-scout/data-collector](https://img.shields.io/npm/v/%40talen
Latest version: 0.1.1

# @talent-scout/data-collector

[![GitHub Actions](https://github.com/presence-io/talent-scout/actions/workflows/publish.yml/badge.svg)](https://github.com/presence-io/talent-scout/actions/workflows/publish.yml)
[![npm: @talent-scout/data-collector](https://img.shields.io/npm/v/%40talent-scout%2Fdata-collector?logo=npm)](https://www.npmjs.com/package/@talent-scout/data-collector)
[![Node.js](https://img.shields.io/badge/node-%3E%3D22-339933?logo=node.js&logoColor=white)](https://nodejs.org/)
[![License: MIT](https://img.shields.io/badge/license-MIT-2ea44f.svg)](../../LICENSE)

`@talent-scout/data-collector` 负责建立候选池。它从 GitHub、社区仓库、榜单页面和 AI 工具生态里收集信号，并把这些原始线索写入 `workspace-data/output/raw/<timestamp>/`。

## 开发前提

- Node.js 22+
- pnpm 10+
- `gh` 已安装并登录
- Playwright 依赖可正常运行

统一在仓库根目录安装依赖：

```bash
pnpm install
```

## 常用命令

```bash
pnpm --filter @talent-scout/data-collector run collect
pnpm --filter @talent-scout/data-collector run build
```

命令应从仓库根目录发起。包内部会利用 `INIT_CWD` 和共享工作区解析逻辑，把输出写到根目录的 `workspace-data/`。

## 采集范围

- 代码仓库中的 AI 工具使用信号，例如 `AGENTS.md`、`copilot-instructions.md`、`.cursorrules`
- commit 历史中的协作和 AI 使用痕迹
- `claude-code`、`mcp-server`、`copilot` 等 topic 相关仓库
- 社区仓库的 contributor、stargazer、fork 网络
- 排行榜和种子列表

## 关键模块

- `src/index.ts`: 采集入口，负责恢复已有结果或启动新的 run
- `src/github-signals.ts`: GitHub 搜索线索
- `src/community.ts`: 社区仓库信号
- `src/rankings.ts`: 排行榜抓取
- `src/stargazers.ts`: AI 工具相关仓库的 stargazer 采集
- `src/follower-graph.ts`: 关注关系扩展的占位实现
- `src/query.ts`: 读取已落盘的 raw 数据

## 设计思想

### 1. 采集要覆盖“显式信号”和“弱信号”

如果只看 AI 工具仓库的 star，很容易把“好奇用户”和“真实高质量开发者”混在一起。所以这个包同时采集：

- 显式信号：配置文件、commit 文本、社区贡献
- 弱信号：stargazer、topic 相关仓库、榜单曝光

处理阶段再决定这些信号如何加权。

### 2. 采集过程必须可恢复

每个采集器都遵循“先检查本地输出，缺失时才执行”的模式。这样一旦排行榜抓取或 GitHub 搜索在中途失败，你不需要从头重新跑整轮采集。

### 3. 工具生态要保持平权

配置里的默认设计把 Claude、Copilot、Cursor、Cline、Windsurf 等工具视为同级信号来源，而不是只偏向某一个生态。这避免候选池被单一社区习惯扭曲。

## 实现流程

```mermaid
flowchart LR
  A[talents.yaml] --> B[GitHub Signals]
  A --> C[Community Signals]
  A --> D[Ranking Sources]
  A --> E[Stargazers]
  B --> F[raw/<timestamp>]
  C --> F
  D --> F
  E --> F
```

## 当前边界

- GitHub Search API 仍然受分页上限约束
- 排行榜抓取依赖页面结构，源站改版时需要修复解析器
- `follower-graph.ts` 目前还不是完整生产实现

## 相关文档

- [03-data-sources.md](../../docs/03-data-sources.md)
- [02-architecture.md](../../docs/02-architecture.md)
npm package: @talent-scout/data-processor
Description: [![GitHub Actions](https://github.com/presence-io/talent-scout/actions/workflows/publish.yml/badge.svg)](https://github.com/presence-io/talent-scout/actions/workflows/publish.yml) [![npm: @talent-scout/data-processor](https://img.shields.io/npm/v/%40talen
Latest version: 0.1.1

# @talent-scout/data-processor

[![GitHub Actions](https://github.com/presence-io/talent-scout/actions/workflows/publish.yml/badge.svg)](https://github.com/presence-io/talent-scout/actions/workflows/publish.yml)
[![npm: @talent-scout/data-processor](https://img.shields.io/npm/v/%40talent-scout%2Fdata-processor?logo=npm)](https://www.npmjs.com/package/@talent-scout/data-processor)
[![Node.js](https://img.shields.io/badge/node-%3E%3D22-339933?logo=node.js&logoColor=white)](https://nodejs.org/)
[![License: MIT](https://img.shields.io/badge/license-MIT-2ea44f.svg)](../../LICENSE)

`@talent-scout/data-processor` 把原始线索变成可评估的候选人。它负责合并、去重、身份识别和规则层评分，是从“线索池”走向“候选池”的关键分水岭。

## 开发前提

- Node.js 22+
- pnpm 10+
- `gh` 已安装并登录

在仓库根目录安装依赖：

```bash
pnpm install
```

## 常用命令

```bash
pnpm --filter @talent-scout/data-processor run process
pnpm --filter @talent-scout/data-processor run validate:identity
pnpm --filter @talent-scout/data-processor run build
```

`process` 会读取最新的 raw 输出，并写入 `workspace-data/output/processed/<timestamp>/`。

## 核心模块

- `src/cli.ts`: 处理入口
- `src/merge.ts`: 候选人合并与信号去重
- `src/identity.ts`: 中文开发者身份识别
- `src/scoring.ts`: 规则层评分
- `src/query.ts`: 读取处理后的数据
- `src/validate-identity.ts`: 身份识别调试脚本

## 设计思想

### 1. 中文身份是硬过滤，不是加分项

这个项目的目标用户群本来就是“值得关注的中文开发者”。因此身份判断应该在评估前完成，而不是把“是否中文开发者”混进最终评分里，否则会把目标画像和能力判断混在一起。

### 2. 用 noisy-or 组合弱信号

身份识别不是单条规则命中就结束。这里采用 noisy-or 思路，把位置、邮箱域名、中文 bio、中文 commit、拼音姓名、UTC+8 活跃模式等弱信号累积成整体置信度：

$$
P(中国) = 1 - \prod_i (1 - p_i)
$$

这样做的好处是：

- 强信号可以直接拉高置信度
- 多个中弱信号可以自然叠加
- 没有信号时不会虚构高分

### 3. 规则评分只负责“稳定、可解释”的部分

`scoring.ts` 只做那些能从 profile 和 repo 特征中稳定算出的维度，例如：

- stars、followers、语言多样性、最近活跃月数
- fork 比例
- 热点追逐和批量 fork 这类反模式

灰区身份和深度技术判断留给 `@talent-scout/ai-evaluator`。

## 实现流

```mermaid
flowchart LR
  A[raw signals] --> B[merge.ts]
  B --> C[identity.ts]
  C --> D[scoring.ts]
  D --> E[processed/<timestamp>]
```

## 算法取舍

- 合并阶段按信号来源去重，避免同一事件在多个采集器里重复加分
- 身份识别保留灰区区间，交给 AI 再判断，而不是强行二分类
- 评分优先保证解释性，避免在规则层引入难以维护的黑盒模型

## 调试建议

- 身份误判优先跑 `validate:identity` 看规则层命中情况
- 如果某类候选人被系统性低估，先检查 merge 和特征提取，再讨论阈值
- 修改评分公式时，要同时关注 `ai-evaluator` 的最终排序是否发生不合理漂移

## 相关文档

- [04-identity.md](../../docs/04-identity.md)
- [05-evaluation.md](../../docs/05-evaluation.md)
- [07-data-model.md](../../docs/07-data-model.md)
npm package: @talent-scout/shared
Description: [![GitHub Actions](https://github.com/presence-io/talent-scout/actions/workflows/publish.yml/badge.svg)](https://github.com/presence-io/talent-scout/actions/workflows/publish.yml) [![npm: @talent-scout/shared](https://img.shields.io/npm/v/%40talent-scout%
Latest version: 0.1.1

# @talent-scout/shared

[![GitHub Actions](https://github.com/presence-io/talent-scout/actions/workflows/publish.yml/badge.svg)](https://github.com/presence-io/talent-scout/actions/workflows/publish.yml)
[![npm: @talent-scout/shared](https://img.shields.io/npm/v/%40talent-scout%2Fshared?logo=npm)](https://www.npmjs.com/package/@talent-scout/shared)
[![Node.js](https://img.shields.io/badge/node-%3E%3D22-339933?logo=node.js&logoColor=white)](https://nodejs.org/)
[![License: MIT](https://img.shields.io/badge/license-MIT-2ea44f.svg)](../../LICENSE)

`@talent-scout/shared` 是整个 monorepo 的基础设施层。它不做业务决策，负责把配置、工作区路径、缓存、GitHub CLI、OpenClaw CLI 和共享类型统一起来，让其他包专注在收集、处理、评估和展示上。

## 开发前提

- Node.js 22+
- pnpm 10+
- `gh` 已安装并完成认证
- `openclaw` 已安装，用于 cron 同步和 agent 调用

在仓库根目录安装依赖：

```bash
pnpm install
```

## 常用命令

```bash
pnpm --filter @talent-scout/shared run build
pnpm --filter @talent-scout/shared run cron:sync
```

`cron:sync` 会读取仓库根目录的 `talents.yaml`，把其中定义的 `openclaw.cron` 同步到本地 OpenClaw。

## 它解决了哪些问题

- 用一个 Zod 校验过的配置入口替代每个包各自读取 YAML
- 用统一的工作区路径解析，保证所有包都围绕 `workspace-data/` 工作
- 用文件缓存和 checkpoint 机制控制高成本 CLI 调用
- 用共享类型把候选人、信号、评估结果和统计结构稳定下来

## 目录职责

- `src/config.ts`: 读取并校验 `talents.yaml`
- `src/workspace.ts`: 解析 `workspace-data/`、`output/`、`user-data/`、`cache/`、`skill-patches/`
- `src/github.ts`: 封装 `gh` CLI 的分页、缓存和结果整理
- `src/openclaw.ts`: 统一 `openclaw agent` 和 `openclaw cron` 的参数编排
- `src/cache.ts`: 文件缓存
- `src/checkpoint.ts`: 可恢复的批处理检查点
- `src/ignore-list.ts`: 跨包共享的忽略名单读写

## 设计思路

### 1. 配置必须是唯一事实来源

所有业务包都通过 `loadConfig()` 获取配置，而不是在包内复制默认值。这样做有两个直接好处：

- 调阈值时不会出现多处不一致
- `skills`、`dashboard` 和业务包能共享同一份运行语义

### 2. CLI 封装要比 SDK 更稳定

这个仓库刻意依赖 `gh` 和 `openclaw` CLI，而不是直接引入 GitHub SDK 或 LLM SDK。原因很简单：模型路由、权限和工作区状态都已经由 CLI 管理，`shared` 只需要把参数约束收口即可。

### 3. 工作区状态要与源码分离

运行时数据全部写到 `workspace-data/`。这让你可以反复重跑 pipeline，而不会污染源代码目录，也方便 Dashboard 和 skills 在不改动业务逻辑的前提下消费同一份结果。

## 实现流

```mermaid
flowchart TD
  A[talents.yaml] --> B[config.ts]
  B --> C[workspace.ts]
  C --> D[github.ts]
  C --> E[openclaw.ts]
  C --> F[cache.ts]
  C --> G[checkpoint.ts]
  D --> H[collector / processor / evaluator]
  E --> H
  F --> H
  G --> H
```

## 修改这个包时的判断标准

- 如果改动会影响多个包的运行语义，优先放在这里统一处理
- 如果某段逻辑只属于一个业务域，不要上移到 `shared`
- 如果新增字段进入 `talents.yaml`，要同步补充校验与默认值策略

## 相关文档

- [02-architecture.md](../../docs/02-architecture.md)
- [06-openclaw.md](../../docs/06-openclaw.md)
- [07-data-model.md](../../docs/07-data-model.md)
npm package: @talentan/tools
Description: tools for self use
Author: az15921869329@gmail.com
Latest version: 0.1.0

<!-- @format -->

### Why this repo?

Small tools for better life

### How to use

#### requirements

node environment

#### install

```javascript
npm install @talentan/tools -g
```

#### examples

```javascript
// 批量重命名文件后缀
talentan resuffix doc txt // 把当前文件夹下(不包括子文件夹)的 *.doc重命名成 *.txt
talentan resuffix doc txt -a // 把文件夹下(包括子文件夹)的 *.doc重命名成 *.txt

```