tapd-login

Original：🇨🇳 Chinese

Translated

This skill is used when users need to log in to the local TAPD CLI, obtain TAPD personal tokens or application credentials, configure authentication, or clear local authentication information via logout.

4installs

Sourceqizhi2design-svg/tapd-skills

Added on2026-04-25

NPX Install

npx skill4agent add qizhi2design-svg/tapd-skills tapd-login

SKILL.md Content (Chinese)

View Translation Comparison →

TAPD Login

This skill is used when users need to configure or clear authentication information for the local TAPD CLI.

Usage Scenarios

First-time configuration of TAPD CLI
Authentication errors occur with
```
tapd
```
Users request to log in, configure tokens, bind credentials, or log out

Recommended Authentication Method

Prioritize guiding users to use TAPD Personal Token. Only guide users through the application credential process when they clearly need open application access.

Personal Token Acquisition Process (Recommended)

When users do not have a

TAPD_ACCESS_TOKEN

, guide them to follow these steps to obtain it:

Open the TAPD Personal Token page:

text

https://www.tapd.cn/personal_settings/index?tab=personal_token

Click "Create Personal Access Token"
Fill in the name or usage description as needed
Copy the token after creation

Important Reminders:

Tokens are usually only displayed once
Users must save the token immediately
If lost later, a new token can only be created

After obtaining the token, proceed to execute the login command.

Application Credential Acquisition Process (Alternative)

If users clearly want to use the open application mode, guide them to:

Create an application in the TAPD Open Platform
Obtain the following information:
- ```
client_id
```
- ```
client_secret
```
- ```
company_id
```
Confirm these values can be used for CLI login before proceeding to execute the login command

If users are unsure which method to choose, default back to the personal token scheme; do not prioritize recommending application credentials.

Execution Steps

First confirm whether the user has obtained the credentials:
- Personal token mode: Requires
```
TAPD_ACCESS_TOKEN
```
  and a
```
workspace_id
```
- Application credential mode: Requires
```
client_id
```
  ,
```
client_secret
```
  ,
```
company_id
```
If the user does not have credentials yet, first guide them to complete the above acquisition process; do not rush to initiate requirement creation or synchronization.
If the user needs to log in, execute:

bash

tapd login

If the user has provided parameters, prioritize using non-interactive mode:

bash

tapd login --mode personal --personal-token <token> --workspace-id <workspace-id>
tapd login --mode app --client-id <id> --client-secret <secret> --company-id <company-id>

If the user wants to clear local authentication information, execute:

bash

tapd logout

Notes

```
tapd login
```
writes credentials to
```
.tapd/credentials.json
```
The personal token mode verifies a workspace simultaneously
```
tapd logout
```
deletes the local authentication file
When users do not have credentials, guide them to obtain credentials first before proceeding to create, synchronize, or pull requirements

tapd-login

NPX Install

Tags

SKILL.md Content (Chinese)

TAPD Login

Usage Scenarios

Recommended Authentication Method

Personal Token Acquisition Process (Recommended)

Application Credential Acquisition Process (Alternative)

Execution Steps

Notes